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

ld-fs-starter

v1.1.0

Published

![File Structure](client/src/logo.svg) This project is meant to be a starting place for a Express server with a React client and a Firebase database. This project uses a Procfile for deployment to heroku, though heroku is 100% optional.

Downloads

46

Readme

FERN Stack Starter

File Structure This project is meant to be a starting place for a Express server with a React client and a Firebase database. This project uses a Procfile for deployment to heroku, though heroku is 100% optional.

Getting Started

Run

npm install

in the root directory of the project.

This will install all the packages needed for the project to build iteself, including the depencies needed by ./server and ./client. NOTE: both of these folders have their own package.json and /node_modules, so keep that in mind when installing additional packages from the terminal.

After successfully installing all dependencies, run:

npm run build

in the root directory.

This should build the server and the client and a ./build folder will be generated in each subdirectory. For the Server, the build script is simply compiling the typescript to javascript, while Client utilizes create-react-app, which comes with webpack to bundle all the dependencies in ./client/src/ then builds out static assets. (The ./client/build folder is what you could copy and past into any public_html and serve up the index.html page inside)

Note: ./server has a tsconfig.json* which defines the input and output files, among other typescript options. Click here for more info about tsconfig.json and how to configure it, should you need to. *(./client does too, but create-react-app manages it)

After both subdirectories have a ./build folder, to run locally run:

npm start

in the root.

There are a number of scripts defined in the root package.json that would be worth reading over to save some time, particularly in development. Furthermore, each subdirectory's package.json has scripts defined, so you could work on each individually.

File Structure

File Structure

Root

package.json: defines metadata of the project, scripts, and dependencies

server/: contains all server related files

client/: contains all client related files

node_modules/: dependencies for ROOT

_media/: assets for README.md, etc

Procfile: defines how the app should start on heroku, required for heroku

.env.sample: file to declare environment variables

Server

src/: file to declare environment variables

build/: file to declare environment variables

node_modules/: dependencies for server

package.json: defines metadata of server project, scripts, and dependencies

tsconfig.json: configuration file for the typescript compiler

Client

src/: file to declare environment variables

build/: file to declare environment variables

public/: index.html lives here, logos, etc

node_modules/: dependencies for client

package.json: defines metadata of the client project, scripts, and dependencies

tsconfig.json: configuration file for the typescript compiler