Releases: EMH333/esbuild-svelte
v0.9.0
This will be the last pre-v1 minor release if all goes according to plan.
- Add support for
*.svelte.js
and*.svelte.ts
Svelte modules (Thank you @ElijahJohnson5 for the contribution!) - Remove support for boolean values for Svelte
css
compile option (useexternal
orinjected
instead) - Bump svelte minimum version to
4.2.1
- Bump esbuild minimum version to
0.17.0
- Bump Node minimum version to 18 (lowest supported by Svelte 5)
- Remove
overzealous
cache option (was unusable) - Remove
fromEntryFile
option (was unusable)
v0.8.2
-
Update Svelte peer dependency version lock to include Svelte 5 pre-release versions (#235)
The version lock will be updated once Svelte 5 is released to remove support for pre-release versions. But for now, this should help prevent needing to use
--force
or--legacy-peer-deps
when using Svelte 5 pre-releases.
v0.8.1
-
Update Svelte peer dependency version lock to include Svelte 5
This should have no impact on Svelte 3 or 4 users, but will allow folks to start trying out Svelte 5 if they so please. Any errors or issues should be reported as bugs in order to resolve them before Svelte 5 is offically released.
Plugin versions
v0.8.x
will be the last to support Svelte 3 and Svelte 4 belowv4.2.1
v0.8.0
-
Minorly Breaking Caching is automatically enabled after two sucessful builds when using the
context
esbuild APIPreviously caching was automatically enabled when using the watch or incremental esbuild options, but those were removed in esbuild
v0.17.0
. This change brings back the automatic cache enabling when using thecontext
API which supports the same features as the previous watch and incremental options. esbuild does not provide a way for plugins to determine if thecontext
API is being used, so this feature is enabled after two successful builds. This should be a reasonable compromise between not enabling the cache at all and enabling it for every build (which wastes time and space if caching isn't needed).If you are using the
context
API and want to disable the cache, you can set thecache
option tofalse
in the plugin options but this isn't recommended (if you do need to disable the cache for some reason, please open an issue to see if your usecase can be fixed). -
Minorly Breaking Add dependency to
@jridgewell/trace-mapping
so error messages are more accurate when using preprocessors (#83)If you are using Svelte 4, this doesn't add additional dependencies because that package is already required by Svelte 4.
-
Update development esbuild version to
0.19.0
This means that this plugin now supports additional inhancements when using the
context
esbuildv0.17.0
API as detailed below.
v0.7.4
- Lock Svelte peerDependency to
>=3.43.0 <5
to protect against breaking changes in future Svelte releases - Set compilerOptions.css to
external
by default if using Svelte v4 or higher (#185) - Add compatibility tests for different versions of Svelte and esbuild to prevent regressions
- Switch development version of Svelte to v4
v0.7.3
- Switch from
.npmignore
tofiles
property ofpackage.json
to prevent accidental file inclusion
v0.7.2
v0.7.1
-
Fix watch mode if preprocessing failed (#132)
-
Remove support for Node 12
This should probably be another breaking change however Node 12 has reached end of life and is no longer supported. If you are using Node 12, please upgrade to Node 14 in order to continue use of this plugin (or open an issue if you disagree).
v0.7.0
-
Breaking Svelte has been switched to a peer dependency which allows Svelte to be updated independently of this plugin
Migration is as simple as
npm i --save-dev svelte
if you don't havesvelte
as a dependency already. -
Breaking Remove
compileOptions
since it was deprecated in v0.6.0
v0.6.3
-
Add
filterWarnings
option to filter the Svelte warnings that esbuild-svelte passes to esbuild (Thanks @Prinzhorn)See
dist/index.d.ts
for the type definition of the new option. This hope is to replicateonwarn
from the Svelte Rollup plugin, but in a way that is more conducive to the way esbuild handles things.