Published by seek-oss-ci almost 2 years ago
Add package.json
configuration flags that enable you to skip sku configuration and peer dep validation (#727)
NOTE: These settings disable critical functionality of sku, so you likely
don't want to use them unless you know what you're doing
skuSkipConfigure
: Skip generation of config files. E.g. .prettierrc, tsconfig.json, etc.skuSkipValidatePeerDeps
: Skip checking for multiple copies of the same package. You likely want to try and fix the warnings found by this check rather than disabling it.EXAMPLE USAGE:
// package.json
{
"skuSkipConfigure": true,
"skuSkipValidatePeerDeps": true
}
Published by seek-oss-ci almost 2 years ago
deps: @pmmmwh/[email protected]
(#716)
Update to eslint-config-seek v10.1.1. Read the following release notes for all the changes: (#718)
Published by seek-oss-ci about 2 years ago
It is highly encouraged that you run npx yarn-deduplicate
after updating to sku 11.6.0 in order to hopefully prevent duplicate packages being in your lock file.
Update to eslint-config-seek v10 (#709)
This update involves a few major version jumps, so be sure to read the following release notes for all the breaking changes:
You should be able to automatically fix most lint warnings/errors by running yarn sku format
.
Upgrade from jest v27 to v29 (#709)
Please take a look at the following upgrade guides as there may be breaking changes that affect your tests:
Likely the most significant change is the new default snapshot format:
- Expected: \\"a\\"
+ Expected: "a"
- Object {
- Array []
- }
+ {
+ []
+ }
This may require you to update your snapshots.
Drop support for Node v12 (#709)
Sku now only supports Node v14.15 and above.
Although sku itself does not depend on any Node v14 APIs, Node v12 is no longer officially supported, and many of sku's dependencies no longer support it either.
Please ensure you are using a supported version of Node both locally (e.g. via a .nvmrc
file) and in CI (check your Docker images).
Update typescript dependency (#709)
Sku now has a typescript
dependency of ^4.5.0
.
Previously the version was restricted due to a type issue with braid-design-system
and [email protected]
.
Please take a look at the release notes for recent typescript versions as there may be breaking changes that need to be addressed.
Published by seek-oss-ci about 2 years ago
Add optional delete-unused-keys
flag to the translations push
command (#702)
If this flag is set, unused keys will be deleted from Phrase after translations are pushed.
sku translations push --delete-unused-keys
sku translations
command is provided (#702)Published by seek-oss-ci about 2 years ago
ReadonlyArray
s, to allow for passing in of as const
arrays.lib
of tsconfig to es2019
, to allow access to all that flatMappy goodness.Published by seek-oss-ci over 2 years ago
Allow :
to be used in dynamic paths again. (#687)
Previously, dynamic paths were declared using the standard :param
syntax, but this had been deprecated in favour of $param
.
This has now been updated to allow for both.
This should allow sku serve
to work for projects using colon syntax.
Published by seek-oss-ci over 2 years ago
Published by seek-oss-ci over 2 years ago
Exclude playroom from vanilla-extract pipeline (#682)
TL;DR Only affects consumers using running Playroom along side sku — i.e. Braid.
Due to the current pattern used for the virtual file paths of vanilla-extract's generated stylesheets, we are manually excluding Playroom’s vanilla-extract styles.
In the future, we are planning to use more realistic virtual file paths, which should honour the default handling of include/exclude path matching and make this work around no longer necessary.
Published by seek-oss-ci over 2 years ago
test: Run Jest using the CI flag when in CI environment (#678)
Tests run in CI should fail if a new snapshot is written, this was not the case and needed to be opted into manually by passing the --ci
flag to Jest.
Published by seek-oss-ci over 2 years ago
Any app that configures languages
will automatically have the en-PSEUDO
language generated for them. (#675)
en-PSEUDO
is a generated language created by pseudo-localizing existing en
translation messages in your app.
An explanation of the pseudo-localization process, as well as possible use cases for this language, can be found in the Vocab docs.
en-PSEUDO
can be consumed just like any other language in your app:
const App = () => <VocabProvider language="en-PSEUDO">...</VocabProvider>;
NB: Statically-rendered apps will not be able to render an en-PSEUDO
version of their app at build time.
If this is a use case that you would find useful, please reach out in #sku-support.