In examples, add "svelte" to conditions in esbuild build options

[BlueGreenMagick]

Problem

Currently, when you try to import a svelte component library, you get the below error when building.

None of the conditions provided ("types", "svelte") match any of the currently active conditions
  ("browser", "default", "import", "module"):

Steps to reproduce:

1. npx degit EMH333/esbuild-svelte/example-ts my-svelte-app
2. npm install svelte-french-toast
3. Add statement import toast from "svelte-french-toast" to code.
4. npm install, npm run build

Solution

The solution is to add conditions: ["svelte"], to esbuild's build options. I had problem figuring it out as I couldn't find this information anywhere. So I added this information to examples in README and example projects.

Svelte plugins for other bundlers like rollup and webpack all state this information in their READMEs:
https://github.com/sveltejs/rollup-plugin-svelte#svelte-exports-condition
https://github.com/sveltejs/svelte-loader#resolveconditionnames

[EMH333]

Ah yep, thanks for documenting that. Do you think this is the sort of thing that esbuild-svelte should add automatically? This seems reasonable along with the change to condition handling for svelte@v4

breaking: Bundlers must specify the browser condition when building a frontend bundle for the browser (sveltejs/svelte#8516)

Please fix the linting issue, I'll merge after that!

[BlueGreenMagick]

Fixed!

Do you think this is the sort of thing that esbuild-svelte should add automatically?

I'm not sure about that either. But the other svelte plugins for rollup and webpack all require manually setting it up, so keeping it that way seemed safer.

breaking: Bundlers must specify the browser condition when building a frontend bundle for the browser (sveltejs/svelte#8516)

Should I add something for this? esbuild automatically include it in conditions if platform is set to "browser"
https://esbuild.github.io/api/#how-conditions-work

[EMH333]

I'm not sure about that either. But the other svelte plugins for rollup and webpack all require manually setting it up, so keeping it that way seemed safer.

Fair enough. I'll keep an eye on it and might consider changing that in a breaking release at some point.

Should I add something for this?

Yeah if you would be willing to add a mention about it that would be great! I'll merge this PR on Monday evening either way. Thanks!

[BlueGreenMagick]

Yeah if you would be willing to add a mention about it that would be great!

Done!