v0.8.0

• Minorly Breaking Caching is automatically enabled after two sucessful builds when using the context esbuild API

  Previously 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 the context API which supports the same features as the previous watch and incremental options. esbuild does not provide a way for plugins to determine if the context 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 the cache option to false 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 esbuild v0.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 to files property of package.json to prevent accidental file inclusion

v0.7.2

• Support string values for Svelte compiler option css added in Svelte v3.53.0 (#109, #150)
• Update misc dependencies

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 have svelte 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 replicate onwarn from the Svelte Rollup plugin, but in a way that is more conducive to the way esbuild handles things.

v0.6.2

• Update Svelte to 3.46.2

• (Unstable) Add "overzealous" cache mode that invalidates the cached version of a file if an imported Svelte component has changed (#102)

  As with the standard caching system, this only applies in incremental or watch modes. This shouldn't be used in most situations, but if files aren't rebuilding when they are expected to, then this can be a helpful step before disabling the cache outright. I'm considering this an unstable feature because I'm not set on this way of doing it. This option may change in implementation, name and/or be removed at any time.

v0.6.1

• Update Svelte to 3.45.0
• Auto create releases
• Rework and improve CI process