Skip to content

sku@12.2.0
Compare
Choose a tag to compare
@seek-oss-ci seek-oss-ci released this 12 Jul 02:34
· 95 commits to master since this release
sku@12.2.0
232ec67
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Minor Changes

  • Export internal Jest configuration as a preset under sku/config/jest. This allows consumers to debug tests in their IDE by specifying the preset in their jest.config.js: (#850)

    /** @type {import('jest').Config} */
module.exports = {
  preset: 'sku/config/jest',
};

  • srcPaths no longer affects tsconfig.json#include. Instead, you can use the dangerouslySetTSConfig option to have more control over which files are included in the type checking process. (#848)

    Previously, sku managed the include field in tsconfig.json, but this was problematic for projects that wanted more fine grained control over what was included and/or excluded from compilation.

    Note: If you were previously using srcPaths for this purpose, you should remove the paths which are not source files.

  • Update tsconfig.json options to match the latest version of the TypeScript compiler. (#844)

Patch Changes

  • Upgrade to TypeScript 5.1 (#844)

  • Update dependency eslint-config-seek. (#844)

    This reverts the autofix for a Cypress rule and improves the performance of linting TypeScript files.

  • The presence of a sku.config.js file previously had an effect on what was included in the tsconfig.json#include array. With the removal of the default include array, this is no longer the case and you might see a TypeScript error like this: (#848)

    error TS18003: No inputs were found in config file '/path/to/project/tsconfig.json'. Specified 'include' paths were '["**/*"]' and 'exclude' paths were '[]'.

    If your project contains only JavaScript files and you see the above error, you should rename sku.config.js to sku.config.ts and the error will go away.

Assets 2