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

@hint/utils-create-server

v3.4.26

Published

hint create server util

Downloads

43

Readme

Create Server (@hint/utils-create-server)

Create a server to run tests

Installation

This package is installed automatically when using npm create hint, no need to do anything from your side.

Architecture

The test web server can run in a different thread (default) or the same one (when in CI or if indicated by the user ) as the tests. The following is a summary on the benefits of each one:

  • Independent:
    • Better isolation
    • Improve the debugging experience (website can load even if the execution is stopped in a breakpoint)
  • Same thread:
    • Less resources needed
    • Faster execution

There main pieces are:

  • index.ts: This is what modules consume. Depending on the configuration or the environment it will use one type of server or another.
  • same-thread-server.ts: The real web server. It uses express and listens to the messages sent by index.ts. This will also be the class used when running in CI. If spawned then it will listen for IPC messages for the configuration.
  • independent-thread-server.ts: It is a "wrapper" on top of same-thread-server.ts. It spawns that process and handles the communication with it asynchronously.

When using a different process, each message sent needs a response to confirm the action has been completed, i.e. if it sends a start message it should receive a start message as well. In the case of same thread all the methods are async as well so both servers implement the same interface and the code does not need to special handle one or the other.

The following is an example of messages used:

{
    "webhint": {
        "type": "start"
    }
}

Please note that all messages are "scoped" to webhint to avoid collision with other possible messages.

IPC serializes the messages to JSON. Unfortunatelly it does not accept replacer/reviver functions. The server configuration accepts Buffers so in order to send the right data we need to manually (de)serialize the messages in both ends.