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

fpack-devserver

v0.1.6

Published

Playing with serving files and websockets in reason to build a devserver for fastpack

Downloads

15

Readme

fastpack devserver playground

This is a playground for developing a devserver for fastpack. The goal is to get it merged in to fastpack.

Usage

fpack-devserver(1)          Fpack-devserver Manual          fpack-devserver(1)



NAME
       fpack-devserver - Run a devserver with fastpack.

SYNOPSIS
       fpack-devserver [OPTION]... [ENTRY]

ARGUMENTS
       ENTRY (absent=./src/index.js)
           The main entry point to bundle.

OPTIONS
       --help[=FMT] (default=auto)
           Show this help in format FMT. The value FMT must be one of `auto',
           `pager', `groff' or `plain'. With `auto', the format is `pager` or
           `plain' whenever the TERM env var is `dumb' or undefined.

       -o DIR, --output=DIR (absent=./bundle)
           The output directory to put files.

       -p PORT, --port=PORT (absent=3000)
           The port to serve files on.

       --proxypath=PATH, --pp=PATH (absent=api)
           The path you want to proxy to the backend.

       --proxyrewrite=PATH, --pr=PATH
           Rewrite the proxy path to this.

       --pt=HOST, --proxytarget=HOST
           The adress of the backend server you want to proxy.

       -s DIR, --source=DIR (absent=./source)
           The source folder to copy files from.

       --version
           Show version information.

EXIT STATUS
       fpack-devserver exits with the following status:

       0   on success.

       124 on command line parsing errors.

       125 on unexpected internal errors (bugs).

Special thanks

@anmonteiro has helped me a lot on discord and I have borrowed most of the fileserver part from his graphql example.

Development

You need Esy, you can install the beta using [npm][]:

% npm install -g esy@latest

Then you can install the project dependencies using:

% esy install

Then build the project dependencies along with the project itself:

% esy build

Now you can run your editor within the environment (which also includes merlin):

% esy $EDITOR
% esy vim

After you make some changes to source code, you can re-run project's build using:

% esy build

And test compiled executable:

% esy ./_build/default/bin/Main.exe