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

@ouellettec/omlette-project-template

v0.3.0

Published

## What is this?

Downloads

13

Readme

Omlette Project Template

What is this?

This repo is a project template creator that allows you to quickly bootstrap a monorepo for a React frontend with a Firebase backend.

How to use it

No need to download this package, simply run npx @ouellettec/omlette-project-template --interactive in your desired directory and the CLI tool will ask you a few questions and take care of the rest!

Once installed, you can open the [Your Project Name].code-workspace in vs code by selecting File > Open workspace from file. It should open a popup in the bottom right corner of the window asking you to install the workspaces recommended extensions, click "Show Recommendations". Install all the recommendations to insure the project's auto formatters and task runners run during development. If it does not appear, you may already have them all installed.

Check the README.md in the project's root folder for information on the template's setup and npm scripts.

What templates are available?

Currently there is a frontend, backend, and web templates. web will setup both the frontend and backend templates.

In the future, we hope to add a react native template.

What does it setup?

|Feature|Environment ( Frontend / Backend )|Template ( Frontend, Backend, Web )| |---|---|---| |React ( Using CRA )|Frontend|Frontend, Web| |Tailwind CSS|Frontend|Frontend, Web| |Firebase Functions|Backend|Backend, Web| |EsLint|Both|All| |Prettier|Both|All| |Jest|Both|All|

Developing this Project

  1. Run yarn in he root directory to ensure you have the node dependencies installed.
  2. Run yarn develop in the root folder.
    • You can run yarn develop --interactive to start the app in interactive mode.
    • All the source files are in the /bin directory.
  3. To debug the code, add debugger to where you want the code to stop.
  4. Open Chrome and navigate to chrome://inspect/.
  5. Click open Open dedicated DevTools for Node.
  6. Type rs into the terminal to restart nodemon and re-execute the script.

Deploying the Project

  1. Login to the NPM account with command npm login --scope=@ouellettec
  2. Run yarn deploy:check to ensure the the package has been linted and tested.
  3. Run yarn deploy:test and check the output to insure the files added are correct.
  4. Delete the .tgz that was created.
  5. Increment the NPM version according to semantic versioning.
  6. Commit the changed npm version.
  7. Create a new release tag on Github.
  8. Run yarn deploy.