feat: publish npm package on release #36
Merged
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.
Build and Publishing Workflow Improvements:
publish.yml
) to automate publishing the package to npm when a new tag is pushed. This workflow uses Node.js 22 and ensures the package is built before publishing.Package Structure and Publishing:
package.json
to@postman/postman-mcp-server
, set the main entry point todist/src/index.js
, defined thebin
field, and specified which files should be included when publishing to npm. Also added aprepack
script to ensure the package is built and synced before publishing, and set the package to be public..npmignore
file to exclude source, test, development, and configuration files from the npm package, ensuring only the necessary distribution files are published.Code and Configuration Updates:
src/index.ts
fromtsx
tonode
to ensure compatibility when running the built JavaScript file directly.dist
directory and all.js
files, preventing linting of build artifacts.