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

@mobilabs/pulsar

v1.3.2

Published

A boilerplate to build complex Web Apps relying on Pakket

Downloads

7

Readme

Pulsar

NPM version GitHub last commit Github workflow Test coverage License

Pulsar is a boilerplate for writing a simple Web App or a PWA App relying on the bundler Pakket.

Quick Startup

You can easily get your first Pulsar Wep App running in a couple of minutes by just typing a few command lines. But first, you need to create an empty folder. It will contain your Web App.

Then, you just need to create a package.json file that contains:

{
  "name": "NameOfYourProject",
  "scripts": {
    "create": "npm install @mobilabs/pulsar && npm run populate",
    "populate": "pixarpulsar populate --name $npm_package_name --author $npm_package_config_name --acronym $npm_package_config_acronym --email $npm_package_config_email --url $npm_package_config_url && npm install && npm run build:dev && npm run test && npm run report && npm run server:dev"
  },
  "config": {
    "name": "John Doe",
    "acronym": "jdo",
    "email": "[email protected]",
    "url": "http://www.johndoe.com/"
  }
}

Replace NameOfYourProject by your project name and fill config with your credentials.

And finally, type in the terminal:

npm run create.

That's almost all! When the script has been executed, your folder contains the following files:

Your project Folder
      |_ .github
      |     |_ workflows
      |           |_ ci.yml     // Github Workflow file (if you use it),
      |
      |_ public
      |   |_ src                // The source files of your app,
      |   |   |_ main.js
      |   |   |_ ...
      |   |
      |   |_ .htaccess
      |   |_ 404.html
      |   |_ index.html
      |   |_ ...
      |
      |_ scripts
      |   |_ build.js.dev.js    // the scripts to build your app,
      |   |_ build.css.dev.js
      |   |_ ...
      |
      |_  test
      |     |_ ...              // Your Mocha, Chai test file,
      |     |_ ...
      |
      |_ .eslintignore          // Files to be ignored by ESLint,
      |_ .eslintrc              // A Configuration file for the ESLint linter tool (if you use it),
      |_ .gitignore             // Files that Git must ignore (if you use git),
      |_ .npmignore             // Files that Npm must ignore (optional),
      |_ .CHANGELOG.md          // The changes between your different versions,
      |_ index.js               // The link to your javascript code,
      |_ LICENSE.md             // The license that applies to your library (here MIT),
      |_ package-lock.json      // The NPM dependency tree,
      |_ package.json           // The NPM package file,
      |_ README.md              // Your README file,

And, your browser displays the Web App at the url http://localhost:8080.

How to build it

In a terminal, type the command:

npm run build:dev

It builds the Web App.

In another terminal type the command:

npm run server:dev

It starts an http server and makes the Web App visible in your browser.

How to create a distribution version

When your development is over, type in a terminal:

npm run build:prod

it creates the folder _app that contains the Web App ready to be deployed. And you can see the final result by typing:

npm run server:prod

Enjoy!

License

MIT.