npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

tranel

v0.3.0

Published

Access cross-process API elegant and natural

Downloads

3

Readme

Tranel

license Build Status Coveralls npm Percentage of issues still open

Worker First DOM Manipulate Library

Characteristics

  • Use DOM API like main thread in dom

Note: you should clean ref in worker

Compatibility

Unit tests guarantee support on the following environment:

| IE | CH | SF | IOS | Android | | ---- | ---- | ---- | ---- | ---- | | 10+ | ALL | 9+ | 9+ | 5+ |

Note: code depend on Proxy API, so you need import Polyfill to compatible with old version.

Directory

├── demo - Using demo
├── dist - Compiler output code
├── docs - Project documents
├── src - Source code directory
├── test - Unit tests
├── CHANGELOG.md - Change log

Usage Instructions

Using npm, download and install the code.

$ npm install --save tranel

For Render Thread:

  <script src="../../lib/tranel.js"></script>
  <script>
    new Tranel().listen("./worker.js").registerGlobal()
  </script>

For Worker Thread:

  importScripts("../../lib/tranel.js");
  new Tranel().listen().registerGlobal()

Then you can use DOM API in worker:

let $wcomputeButton = document.getElementById('wcompute');
let $wresult = document.getElementById('wresult');
let $input = document.getElementById('input')
$wcomputeButton.addEventListener('click', () => {
  $wresult.innerText = $input.value
})

Open demo get more example.

Documents

API

Contribution Guide

How to switch JS and TS

  • srctype and scripts in package.json
  • require file of test/test.js
  • require file of test/browser/index.html

For the first time to run, you need to install dependencies firstly.

$ npm install

To dev & serve demo

$ npm run dev

To build the project:

$ npm run build

To run unit tests:

$ npm t

Note: The browser environment needs to be tested manually under test/browser

Modify the version number in package.json, modify the version number in README.md, modify the CHANGELOG.md, and then release the new version.

$ npm run release

Publish the new version to NPM.

$ npm publish

Contributors

contributors

Change Log

CHANGELOG.md

Current Users

Relative links