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

FrontEndCentral-documentation

v2.1.0

Published

Componentized FEC

Downloads

7

Readme

Front End Central Angular2

Componentized FEC

Initial Setup

npm install

Retrieve the required modules such as typescript and webpack. Type definition is managed by @types and included in tsconfig.json.

npm run build

Pack up this document site. If you are going to run 'npm run server' to host the app, this step is not required, and you don't have to re-run after each change, otherwise, re-run will be required. If you are going to publish or contribute to existing/new component, this step is also not required.

npm run server

Host the app locally on http://localhost:3000/

npm run server:hmr (deprecated)

Enable hot module replacement on server, for better experience, please visit http://localhost:3000/webpack-dev-server/ instead. Warning: HMR will not work on doc/index.html, which is the default page of doc app.

Build Details

npm run clean

This will clean all unnecessary files in src/components.

Contributing

  • run npm run server, which will compile typescript and serve the project page locally
  • you should have a server running on localhost:3000 serving the docs
  • for better developing experience, it is highly recommended to use localhost:3000/webpack-dev-server/
  • local server will be available when the log shows webpack: bundle is now VALID.
  • create/update your components
  • before publishment your component to npm, use webpack to pack up your component
  • when you're done, make sure you publish the components that you updated to npm by doing npm run vpublish [component name] ex. npm run vpublish fec-nav

Testing

npm run build:test

Compile and output the test bundle to /test/js with SpecRunner.html in /test. The SpecRunner is only supported by webpack-dev-server. Therefore, if you would like to run all the tests in the browser, npm run server is required. All the tests can be executed at http://localhost:3000/test/SpecRunner.html

For Karma, you can simply run karma start from project root, and webpack will handle everything for you.

Regenerating document HTML

Pandoc is required. Install Pandoc in OS X with brew install pandoc. Instructions for other systems are at pandoc.org.

# From project root:
./pandoc-build.sh

This bash script iterates through component source directories and runs a simple conversion on each README.md document, outputting to /doc/views/<component-name>/README.html.