fix!: do not auto-discover and run a server.js file on npm start#262
Merged
Conversation
BREAKING CHANGE: If a package has a server.js file but no start script, it will no longer be automatically run when the start event is triggered. This change removes the implicit behavior of running server.js and requires an explicit start script to be defined in the package.json.
wraithgar
changed the title
npm start
wraithgar
approved these changes
Apr 14, 2026
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
2 participants
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.
BREAKING CHANGE: If a package has a server.js file but no start script, it will no longer be automatically run when the start event is triggered. This change removes the implicit behavior of running server.js and requires an explicit start script to be defined in the package.json.