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

poly-next

v0.0.11

Published

Modules for end to end app development. Build with Polymer, React, ES6 / ES.Next Code and TypeScript.

Downloads

35

Readme

poly-next

Modularize your entire app developement. Build with Polymer, React, ES6/ES.Next Code and TypeScript.

This project is about modules and using them build your app from end to end.

Quick Start

Use with single module from command line like:

npm install -g poly-next

# then using this repos example
git clone https://github.com/jrmerz/poly-next
cd poly-next/example

poly-next -r app -m elements -t

Please see /example directory for example project layout.

Separation of Concerns

I'm a big fan of Polymer but I want to re-use as much code as possible, have no business logic wrapped up in web components, be able to use standard mocha/chai to test my code (as much as possible) without involving the browser.

How this project works

You write modules. Modules for your client, modules for your server, modules for both. If you need a UI component, you can write Polymer or React. For Polymer, you also include a .html file with the <dom-module /> template (No JS). You can write both ES6 JS and JSX code as all code will go through Browserify + Babel + React + Typescript compile (optional). The server (middleware see poly-next-core) will pre-bundle your code into a single (virtual) html imports file with source maps. So all will look as you wrote it on your desktop in the browser. When you are ready, you can dump the imports file to your /dist dir.

Config

You just need to set

  • The root of the webapp
  • The root of your code to crawl

Default Config

{
    root : path.join(process.cwd(), 'app'),
    port : 8080,
    modules : [],
    servePolyfill : true,
    browserify : {
        debug: true
    },
    typescript : true, // use typescript compile
    tsify : { // only required if above flag is true
        target: 'es6',
        emitDecoratorMetadata : true,
        removeComments : false,
        noImplicitAny : true,
        experimentalDecorators : true,
    },
    babel : {
        presets : ['es2015', 'react'],
        extensions: ['.js', '.ts', '.jsx', '.tsx' ]
    }
}

Sample Config

{
    root : '/path/to/app/root/public',
    port : 8080,
    servePolyfill : true,
    modules : [{
        urlpath : 'elements',
        name : 'bundled_index'
    }],
    typescript : false,
    browserify : {
        debug: true
    },
    babel : {
        presets : ['es2015', 'react']
    }
}

The above sample will server http://localhost:8080/ and provide a html imports file @ http://localhost:8080/elements/bundled_index.html

Polyfills

While servePolyfill=true, the webcomponent polyfills will be served from:

  • /webcomponentsjs/full.js
  • /webcomponentsjs/lite.js
  • /webcomponentsjs/micro.js

Middleware

Checkout the poly-next-core

Command Line Help

poly-next -h

Final Bit

This project is a thought experiment. Please feel free to add yours.