sku@15.0.0
Major Changes
-
Drop support for Node.js versions below 22.19.0 (#1419)
BREAKING CHANGE:
The minimum supported Node.js version is now 22.19.0. Consumers must upgrade to Node.js v22.19.0 or later.
-
Drop
sku initin favour of@sku-lib/create(#1421)BREAKING CHANGE:
The
sku initcommand will now no longer do anything and will display a deprecation notice when used.
It will be removed entirely in a future major version.To create a new
skuproject, use@sku-lib/createinstead. Example usage:pnpm dlx @sku-lib/create my-app -
Throw on invalid
--configfile path (#1420)BREAKING CHANGE:
skuno longer falls back to default sku config files when the config file specified with the--configflag cannot be found.
It will now throw an error and exit the program instead.This ensures users are aware that the configuration file is either missing or incorrectly specified, rather than silently falling back to a default configuration that may not be appropriate for their use case.
If you encounter this error, ensure that the
--configflag points to a valid configuration file. -
Throw error when given unsupported arguments. (#1418)
This is now the default behaviour of the updated commander.js version.BREAKING CHANGE:
Excess command-arguments will now cause an error.
To fix this, remove any unsupported arguments provided to the command.sku build extra-arg # Error > error: too many arguments for 'build'. Expected 0 arguments but got 1. sku build # Fix
-
Default values for entry files use
.tsxextensions instead of.js: (#1420)BREAKING CHANGE:
The following
skuconfig options have had their default values changed.clientEntry:'src/client.js'→'src/client.tsx'renderEntry:'src/render.js'→'src/render.tsx'serverEntry:'src/server.js'→'src/server.tsx'
Existing projects with
.jsentry files will need to either rename their files to.tsxor explicitly specify the.jspaths in their sku config:// sku.config.ts export default { + clientEntry: 'src/client.js', + renderEntry: 'src/render.js', + serverEntry: 'src/server.js', // ... rest of config }
Minor Changes
-
Vite and Vitest can be used without experimental flags (#1424)
The Vite bundler and Vitest test runner now have stable support and can be used in production for static apps.
See sku's vite documentation for more information and migration guidance.
Patch Changes
- Updated dependencies [
7ad51f4]:- @sku-lib/utils@1.0.0
- @sku-lib/vite@1.0.0