Comparison with @evanw code

[pjebs]

I was wondering what the difference was between your plugin and the code on evanw's esbuild documentation.

I've studied your code and don't 100% understand that differences.

From what I've gathered:

1. You now run svelte.compileModule() for files with *.svelte.js and *.svelte.ts extensions.
2. There is some kind of caching involved. I don't understand how it works though or what it's trying to achieve.

My aim is to build a Go port of your plugin.

[EMH333]

(I've moved this to a discussion since this isn't an issue directly with esbuild-svelte)

A noble quest! Please keep me updated with your progress!

There are many features added to esbuild-svelte compared to the example plugin provided by evanw. For example:

• Supports bundling css into a separate file
• Supports Svelte 5 and *.svelte.js/ts files
• Allows users to pass in Svelte preprocessors to run before compiling a Svelte component
• Caches compiled files for reduced recompilation time. This also takes into account the dependencies of those files and will invalidate properly if a downstream dependency changes
• Allows filtering of warning messages passed back to the user

And several other things I'm sure I'm forgetting. The original version of this plugin was published over 5 years ago at this point so it has gone through a great deal of iteration and development to be reliable and effective for it's purpose.

[pjebs]

How important is the caching? How much does it improve performance?

[EMH333]

Caching only comes into play when watch mode is active. It means the only thing which is recompiled is the file that changed instead of (potentially) the whole project. This was something I added later, and was difficult to get right (see #59) so I'd skip it for an initial proof of concept.

The gains can be significant, but it varies wildly based on the size, complexity and number of files which need to be compiled