Security News
The Push to Ban Ransom Payments Is Gaining Momentum
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
builder-docs-archetype-dev
Advanced tools
Changelog
6.0.1 (2017 May 02)
Readme
A Builder archetype for Formidable static React landers.
./static-routes.js
file that exports an array
of all the routes your heart desires.module.exports = [
"/",
"/about",
"/pineapples"
];
To release a project controlled by this archetype (e.g., victory-docs
),
use the following guide:
IMPORTANT - NPM: To correctly run preversion
your first step is to make
sure that you have a very modern npm
binary:
$ npm install -g npm
Built files in build/
should not be committed during development or PRs.
Instead we only build and commit them for published, tagged releases. So
the basic workflow is:
# Make sure you have a clean, up-to-date `master`
$ git pull
$ git status # (should be no changes)
# Choose a semantic update for the new version.
# If you're unsure, read about semantic versioning at http://semver.org/
$ npm version major|minor|patch -m "Version %s - INSERT_REASONS"
# Push the `build/` directory, version commits, and tag:
$ git push --follow-tags
# And finally publish to `npm`!
$ npm publish
And you've published!
For a reliable systems of releases, the landers should aim for versioning along these lines:
For additional information on the underlying NPM technologies and approaches, please review:
npm version
: Runs verification,
builds build/
via scripts
commands.npm publish
: Uploads to NPM.This section applies to the archetype itself (builder-docs-archetype
).
You can read the Builder docs for the full story. Here is an overview of the Builder three-way dependency scheme:
package.json:dependencies
: Production dependencies for the archetype
installed in a project.dev/package.json:dependencies
: Development dependencies for the archetype
installed in a project.package.json:devDependencies
: The development dependencies used internally
for the this archetype during development (self tests, checks, etc.) that
are not part of the overall archetype outside workflow.Run npm run builder:check
For tagged official releases only of the archetype, make sure to:
package.json
versionARCHETYPE-dev
package.json
$ vim package.json # Bump version
$ vim CHANGELOG.md # Add version notes
$ builder-support gen-dev # Generate `dev/*` files
$ npm run builder:check # Last check!
$ git add package.json dev
$ git commit -m "Version bump"
$ git tag -a "vNUMBER" -m "vNUMBER - INSERT_REASONS" # Create tag
$ git push --follow-tags
$ npm publish # Publish main project
$ cd dev && npm publish # Publish dev project
FAQs
An archetype for building static landing/documentation pages for our projects. (Development)
We found that builder-docs-archetype-dev demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 8 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
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
Application Security
New SEC disclosure rules aim to enforce timely cyber incident reporting, but fear of job loss and inadequate resources lead to significant underreporting.
Security News
The Python Software Foundation has secured a 5-year sponsorship from Fastly that supports PSF's activities and events, most notably the security and reliability of the Python Package Index (PyPI).