Svelte on m1 bug with precompiled svelte/internal sources. about esbuild-svelte HOT 7 CLOSED

Any particular reason you also opened an issue with esbuild (evanw/esbuild#699)? Unless there is something clear that points to an issue within esbuild itself, it likely won't be the place to find a solution.

This sort of error hints at problems importing a svelte module. The source code, file structure and zip you included seem to be three different projects (one is using svelte-slidy, the another is svelte-slidy from what I can tell) so I'm having a hard time determining exactly where the problem is and what to look for. Some guidance here would be very helpful.

I would confirm that all the required svelte modules are being imported correctly. If you are attempting to create a node library or package, set the platform esbuild option to 'node'. Then, for the actual application being served to users, I would highly recommend allowing the svelte sources to be bundled (platform: 'browser' and remove them from external).

from esbuild-svelte.

Yes, you are right, it's not esbuild or you's plugin bug.
It's bug in svelte/internal/index.mjs file - this expression not working properly in esbuild bundle on m1 mac arm64 processor. But strange, it's working on x86 architecture 🤷🏻‍♂️

if you have arm64 m1 mac - you can see this issue in .zip on dev mode - npm run dev

This is screen for proposal change script with checking props. & without checking this outros it's undefined...

from esbuild-svelte.

Interesting! I'm glad you were able to find the root source of the problem!

from esbuild-svelte.

Interesting! I'm glad you were able to find the root source of the problem!

Me too very interesting ))) how it's working with others behaviour arm64/x86 architecture 🤔

Which format you are recommend for platform browser?

from esbuild-svelte.

It's surprising that you are seeing a difference based on architecture. That shouldn't be the case. Are you sure your environments are identical?

IIFE (the default) is probably fine, that is what Evan recommends and it should see a few optimizations in the next few months

from esbuild-svelte.

Yep! Environments are identical. Only different processors.🤷🏻

from esbuild-svelte.

Tx @AlexxNB for adviced & help 👍🏻 with another solution
His fix when m1 missed svelte package path for esbuild:

function fix_svelte_path() {
    return {
        name: 'fix_svelte_path',
        setup(b) {
			const path = require('path')
            b.onResolve({ filter: /^svelte$|^svelte\// }, args => {
                return { path: path.join(__dirname,'node_modules',args.path,'index.mjs') }
            });
        }
    }
}

...
plugins: [
    fix_svelte_path(),
    ...

from esbuild-svelte.