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

sep4-iot-greenhouse

v0.1.0

Published

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app) using npx create-react-app.

Downloads

5

Readme

This project was bootstrapped with Create React App using npx create-react-app.

React

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm test --coverage

To generate the coverage report

Docker

cd to the frontend folder

Available Scripts

docker run -p 8080:3000 -d greenhouse

to run the app in a new container Open http://localhost:8080 to view it in your browser.

docker start

to run the app in a already made container Open http://localhost:8080 to view it in your browser.

docker images

to see all images

docker stop ccfac1f88d1b or docker stop greenhouse

to stop the docker container from running use

docker kill <container_id_or_name>

to force stop the container from running

docker rm <container_id_or_name>

to remove the container

Build by

### docker build -t greenhouse .

Docker compose

docker-compose up

to run docker compose

docker-compose down

stops and deletes the container but images and volume still remain

Deployment to Github Pages

make sure you are on gh-pages branch

Available Scripts

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run deploy

This command uses the gh-pages npm package to publish your build directory to the gh-pages branch of your repository. Make sure to bring changes to Main before running this command because it changes the structure.

npm cache clean --force

In some cases, clearing the npm cache can resolve issues related to package installations.

rm -rf node_modules package-lock.json then npm install

If you have serious issues, try deleting the node_modules directory and the package-lock.json file, then reinstalling the dependencies: