Releases: springernature/frontend-package-manager
Releases · springernature/frontend-package-manager
9.0.0
8.0.0
- Updates to
dart-sass
node-sass
no longer supported
7.0.0
- This release provides tighter controls on package folder structures by validating against the 'CSSDirectoryStructure' key if it is present in the
package-manager.json
config. If folders exist that don't match those in the config then validation will fail. - Also includes dependency updates.
6.0.0
Adds validation
and publication
steps for generating a static/standalone demo of a component for use within a Living Styleguide
- Check for
demo
folder containing (some of)handlebars
,scss
,js
,json
- Validate compiling/transpiling of assets found
- Generate a static
index.html
file using compiled assets and store it indemo/dist
- Publish this folder with the rest of the code to NPM
5.0.0
- Major rewrite that requires a change to repo structures
- Move to a single, cross-brand context package
- Context package now lives in a separate location with its own validation
- Remove package extension
- Cross-brand packages now live in a single toolkit with brand configurations
- Refactor of existing code
4.0.0
- Major rewrite that requires a change to repo structures
- Handles multiple toolkits per repo
- Will NOT work on old repo structure
- Remove the ability to configure the
packagesDirectory
- Switches from Promise to Async/Await
3.0.0
- Move some functionality out into utility modules
- Standardise reporting
- Handle HTTP errors when checking and downloading from NPM registry
1.0.0
First stable release. Removes dependency on npm-utils