
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
builder-support
Advanced tools
Support tools for authoring builder archetypes.
To use the production and development workflows, install both this package and the development module:
$ npm install --save-dev builder-support
Use this tool to create an ARCHETYPE-dev
module for publishing alongside
ARCHETYPE
with the same version numbers, details, etc.
This tools assumes an archetype structure of:
package.json
- Dependencies needed for production tasks and scripts
entry
that has tasks for both production and development. Must have name
,
description
fields.dev/package.json
../ARCHETYPE-dev/package.json
Assuming those exist, then the tool:
Modifies ARCHETYPE-dev/package.json
as follows:
package.json
package.json:devDependencies
package.json:dependencies
with
ARCHETYPE-dev/package.json:dependencies
name
field to represent ARCHETYPE-dev
Copies README.md
to ARCHETYPE-dev/README.md
Copies .gitignore
to ARCHETYPE-dev/.gitignore
This supports a workflow as follows:
$ vim HISTORY.md # Version notes
$ vim package.json # Bump version
$ builder-support gen-dev # Generate `ARCHETYPE-dev` files
$ npm run builder:check # Last check!
$ git add .
$ git commit -m "Version bump"
$ git tag -a "vNUMBER" -m "Version NUMBER"
$ git push && git push --tags
$ npm publish # Publish main project
# Publish dev project in same repo
$ cd dev && npm publish
# (OR) Publish dev project in different, parallel repo
$ cd ../ARCHETYPE-dev
$ git commit -m "Version bump"
$ git tag -a "vNUMBER" -m "Version NUMBER"
$ git push && git push --tags
$ npm publish # Publish dev project
If you are bootstrapping a new archetype you will need to ensure either that
a ARCHETYPE/dev
or ../ARCHETYPE-dev
directory exists. The rest of the files
when then be properly generated into the dev project.
And you should be good to run builder-support gen-dev
in the project root.
0.5.0
package.json
mutations for ../ARCHETYPE-dev
scenario.FAQs
Builder support libraries
The npm package builder-support receives a total of 4 weekly downloads. As such, builder-support popularity was classified as not popular.
We found that builder-support demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 22 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.