An error happening when webworkers are implemented on next js

[muhammedfouzan]

"@jbrowse/core": "^2.10.2",
"@jbrowse/react-linear-genome-view": "^2.10.1",
"next": "^14.0.4",
"react": "^18.2.0",
"react-dom": "^18.2.0",

state = createViewState({
assembly: config?.assembly[0],
tracks: config?.tracks,
defaultSession: config?.defaultSession,
aggregateTextSearchAdapters: config?.aggregateTextSearchAdapters,
// configuration: config?.configuration,
configuration: {
rpc: {
defaultDriver: "WebWorkerRpcDriver",
},
},
makeWorkerInstance,

    hydrateFn: hydrateRoot,
    createRootFn: createRoot,
  });

[cmdcolin]

i updated our examples including nextjs to use webworkers lately here and didn't see the same error you are seeing. latest code at https://github.com/GMOD/jbrowse-react-linear-genome-view-nextjs-demo/tree/main

...i am familiar with that error in another context (export svg) but a fix was deployed for that GMOD/jbrowse-components#4136 and i even noted that this could be an issue that potentially could arise, however, in practice, i am not seeing it.

your code looks correct so either a) my demo is not correct and maybe is not using webworkers (i think it is though? console.logging appears to show it is!) or b) your webworker setup or nextjs version or jbrowse version could have something to do with it

if you can cross reference vs the example repo that would be great

[muhammedfouzan]

It is a weird issue, I cloned your repo, updated its package.json and next config file with mine, and still your repo works, but the same does not work in mine.
I used the same jbrowse config and page component of your repo in mine.

what else could be the reason, its not the package.json or next.config.ts. since I tried those of mine in yours

[cmdcolin]

can you get exact versions of packages used with e.g. "yarn why @jbrowse/react-linear-genome-view", "yarn why next", "yarn why react"

[muhammedfouzan]

=> Found "@jbrowse/react-linear-genome-view@2.11.1"
=> Found "react@18.3.1"
=> Found "next@14.2.3"

[muhammedfouzan]

I tried installing all module with yarn, instead of npm and it fixed the issue for me. Weird though, I'm assuming it to be something to do with my package-lock.json