Published by seek-oss-ci almost 6 years ago
7.0.0 (2018-12-03)
Migration guide
Bug Fixes
Features
- test: Support test framework setup via ‘setupTests’ script (#216) (2c5465b)
- Add supportedBrowsers option and default to seek config (#222) (90bbeb2)
- Generate ESLint config files (#214) (9fc55ae)
- Introduce new render API (#215) (3e000f4)
- Support source maps for local development (#215) (3e000f4)
- Support library builds (#211) (d981e05)
- Transform ‘compilePackages’ code in tests (#213) (2a4c683)
BREAKING CHANGES
- entry config object has been removed in favour of specific entry values
- entry config object has been removed in favour of specific entry values
- locales config has been removed in favour of sites.
- env is deprecated and considered harmful, apps should move to the new environments config.
- Render entry API has changed.
- Relying on the existence of styles.css or main.js is no longer valid.
- Build output structure has changed and could break current deployment strategies.
- braid-design-system is no longer auto-mocked in tests
- Removed support for monorepos.
- Update SSR port config.
Published by seek-oss-ci almost 6 years ago
6.0.0 (2018-11-01)
Features
- configure: Control gitignoring of sku-created config files (#193) (c4cb532)
- lint: Add TSLint to lint script (#194) (1ac5126)
- typescript: Add support for TypeScript (#192) (16e06b9)
- Support ignore files and control config in project root (#195) (26e925b)
Performance Improvements
- Switch to fast-glob and ignore node_modules in TS check (7107749)
BREAKING CHANGES
- The introduction of controlled configuration files in the project root means consumers may need to take manual action to remove custom configuration files from version control. See the migration guide below for more information.
Migration Guide
New configure step
sku now has the concept of “controlled configurations”, which refers to configuration files that are dynamically generated in the project root, but managed by sku. Adding these files improves editor integration for tools such as prettier and TypeScript, while adding them to .gitignore keeps them a platform concern rather than that of a project.
The configure step will run as a post-install and will re-organise the .gitignore file in your project using ensure-gitignore. All sku controlled ignores will now appear in a block, eg:
my_project_specific_ignore/
# managed by sku
...
ignores_controlled_by_sku/
...
# end managed by sku
Any changes made within the bounds of the comment block will be re-written on the next run of configure (i.e. every npm install).
Please assert that the changes in this file make sense.
Prettier improvements
If you have previously added .prettierrc to your project it is recommended you remove it from version control. sku will now generate a controlled config file for you, ensuring it’s always consistent with the sku format/sku lint commands.
In addition, previously there was no way to control what files Prettier ran on. The format and lint commands now run on all supported file formats (eg. js,ts,tsx,md,less and css), not just the files in your src folder.
If you want to opt out of any specific patterns you can do so by adding them to a .prettierignore file in the root of your project.
$ git rm .prettierrc
$ npm run format
# then stage & commit the change
Published by seek-oss-ci about 6 years ago
5.12.0 (2018-10-16)
Features
Migration Guide
Babel Polyfill
If you're using babel-polyfill, please ensure you upgrade to @babel/polyfill
Update your package.json
"dependencies": {
...
- "babel-polyfill": "^6.26.3"
+ "@babel/polyfill": "^7.0.0"
...
}
Update your consuming code (if managing via sku.config.js)
polyfills: [
...
- 'babel-polyfill'
+ '@babel/polyfill'
...
]
Update your consuming code (if managing directly)
-require("babel-polyfill");
+require("@babel/polyfill");
