Repository navigation
Add fulmine.js - #486
Open
nigrosimone wants to merge 1 commit into
Open
Add fulmine.js#486nigrosimone wants to merge 1 commit into
nigrosimone wants to merge 1 commit into
Conversation
nigrosimone
marked this pull request as ready for review
October 7, 2026 05:13
Member
|
Let's wait a bit to see if the downloads go up! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds fulmine.js, an Express compatible framework. As the requirements ask, it runs on the Node.js HTTP module:
http.createServer(app), with the same route and settings asexpress.cjs.fulmine.js depends on µWebSockets.js for its own
app.listen(), which is not used here. To make this clear, the override in package.json puts an empty package in its place (lib/no-uws), so it is not even downloaded, and it throws if anything loads it.It is already in other benchmarks:
About the 500 downloads per week: the project started in August 2026, so the weekly number is not yet stable above 500 (between ~130 and ~1000 in the last weeks). The repository is active.
The range is
^5.21.5because ofmin-release-age=7in.npmrc. Tested withnpm i --ignore-scriptson Node 20, 22 and 24.