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

codetodestiny-js-starter

v2.0.2

Published

A starter kit for building web applications by Thomas_Okram(founder - Code To Destiny) for the JavaScript and FullStack Programs

Downloads

3

Readme

Code To Destiny | JavaScript Starter Template 2.0

This is the new version of the create-js-app that incorporates the Vite development tool instead of the Parcel bundler as used in v1.0 of this utility. Vite (https://vitejs.dev) brings tremendous performance boost to the development environment.

A sample application has been made available in the src folder which you can edit as needed.

  • src/index.html : This is the root HTML document

  • src/js/index.js: This is the main JavaScript file which is imported into the HTML document. You can directly start building the application here. When you open this file, you will see some code present already. More on this below.

  • src/css/style.css: This is the main stylesheet. Feel free to edit its contents.

  • src/api: This folder contains scripts that provide a simulated backend that you can use in development, if needed. This is powered by Mock Service Worker (https://mswjs.io). If you're building data/remote API based apps, you can use this utility to simulate an API without actually building one during development.

    • src/api/browser.js: Please do not edit this file. It enables the use of Mock Service Worker.
    • src/api/routes.js: This file may be edited to incorporate custom API routes for Mock Server Worker. By default, a root route (/) that returns a text message as a JSON object is present. You can learn more about MSW and how to define your own custom API routes for development by visiting https://mswjs.io/docs/
  • src/public: This folder contains the MSW utility file (mockServiceWorker.js) which should not be edited/removed. Any files you place in this folder can be directly accessed in your HTML document. Use this for placing static assets such as images.

Instructions

  • Development : Run npm run dev - This will start the development server and open the app in the default browser. You can then work with the files in the src/ folder and can see instant updates in the browser.
  • Production Build: Run npm run build - This will produce a build edition that you can then deploy on the cloud/host on a static file service such as GitHub pages or surge.sh. We recommend trying https://surge.sh for deploying static apps. Please note that the build also copies down the mockServiceWorker.js file into the dist folder. You can safely remove this file from the dist folder before deploying your app.