Differences between esm.sh and self hosting

[oravecz]

I am hosting esm.sh internal in our company. Building Fluent UI from Microsoft works on the public esm.sh server, but not on my internal version.

curl 'http://localhost:5050/@fluentui/[email protected]'
"../../.esmd/npm/@fluentui/[email protected]/node_modules/.pnpm/@[email protected]_@[email protected][email protected]/node_modules/@fluentui/react-shared-contexts/lib/ThemeContext.js" for import "ThemeContext"

I am running the server from command line with

• Node 22.10.0
• go version go1.22.5 darwin/arm64
• esm.sh v135_7

ESM Config

{
  "port": 5050
}

[ije]

i also can't build it on my computer(macos m1), will look in to it!

[oravecz]

Looking as best I could, I am unsure how the platform plays a role in being able to resolve the import "ThemeContext".

The react-shared-contexts/index.js is the default export for the package, and it contains the following export.

export { ThemeContext as ThemeContext_unstable, ThemeProvider as ThemeProvider_unstable } from './ThemeContext';

So, I am unsure what (in this package) is attempting to resolve `import "ThemeContext"

Sadly, the latest version (9.21.1) has a different issue.

curl 'http://localhost:5050/@fluentui/[email protected]'
esbuild: Detected cycle while resolving import "CustomStyleHooksContext"