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

noflo-webpack-config

v2.0.3

Published

Base webpack configuration for NoFlo component projects

Downloads

17

Readme

Base webpack configuration for NoFlo component projects

This repository aims to provide a reusable WebPack configuration for NoFlo component projects, primarily aimed at CI usage.

Build setup

You need to add the following development dependencies:

  • webpack
  • webpack-cli
  • noflo-component-loader
  • noflo-runtime-headless
  • noflo-runtime-postmessage

Then add a build command to your NPM scripts:

"build": "webpack --config node_modules/noflo-webpack-config/webpack.config.js",

Now you should be able to make a browser build of your components with npm run build.

Note: if you have CoffeeScript dependencies, install also the coffee-loader package.

Testing components with fbp-spec in browser

You need to add the following development dependencies:

  • fbp-spec

Then add a test command to your NPM scripts:

"test:fbp-spec": "fbp-spec --address ws://localhost:3569 --command \"noflo-runtime-headless -f dist/test.js\" spec/*.yaml",

Now you should be able to run fbp-specs in a browser with npm run test:fbp-spec.

Testing components with Mocha in browser

You need to add the following development dependencies:

  • chai
  • karma
  • karma-chai
  • karma-chrome-launcher
  • karma-mocha
  • karma-mocha-reporter

Then add a test command to your NPM scripts:

"test:mocha": "karma start node_modules/noflo-webpack-config/karma.config.js",

Now you should be able to run Mocha tests in a browser with npm run test:mocha.

Notes:

  • noflo, chai and baseDir are available globally, so no need for additional requires in your test files
  • the test files should be located in spec/*.js or spec/**/*.js

Changes

  • 2.0.3 (October 14th 2020)
    • Made EventEmitter polyfill available by default
  • 2.0.2 (October 14th 2020)
    • Made it easier to extend the webpack config via require('noflo-webpack-config')
  • 2.0.1 (October 13th 2020)
    • Now HTML files in the dist folder will also be served by Karma for test purposes
  • 2.0.0 (October 13th 2020)
  • 1.1.0 (December 8th 2018)
    • Fixed baseDir setting to process.cwd()
    • Added basic usage documentation
    • Added example Karma configuration
  • 1.0.0 (December 8th 2018)
    • Initial version