SharedWorkers are not actually shared across tabs

[krpatter-intc]

🐛 bug report

SharedWorkers do not work. The code below appears to work in the fact that you get a worker, but parcel's adding of ?<timestamp> prevents multiple tabs from getting the same worker.

this.worker = new SharedWorker(new URL("worker.ts", import.meta.url), {type: "module"})

I can't find anyway to make this code not add the ?<timestamp> during the fetch.

The docs explicitly mention that SharedWorker is supported, but there's no recipe given like the other workers, so I suspect maybe this wasn't tested with multiple tabs (since it does appear to work like the new Worker code).

🎛 Configuration (.babelrc, package.json, cli command)

CLI:

start": "parcel serve src/demo-app/index.html --dist-dir build

🤔 Expected Behavior

The ?timestamp can't be added for sharedworkers so that each web page gets the same worker

😯 Current Behavior

Each tab gets a new worker. This can be seen using: chrome://inspect/#workers to view the workers when new tabs are open.

💁 Possible Solution

...

🔦 Context

Trying to use SharedWorkers in a web app to help communicate data amongst multiple tabs.

💻 Code Sample

🌍 Your Environment

Software	Version(s)
Parcel	2.12.0
Node	10.8.2
npm/Yarn
Operating System	Windows

[devongovett]

That's added here:

parcel/packages/runtimes/js/src/JSRuntime.js

Lines 693 to 695 in 0e08d8c

	if (options.hmrOptions) {
	res += ' + "?" + Date.now()';
	}

Perhaps SharedWorkers could be detected and skip this

[krpatter-intc]

I searched through the docs, but didn't see a way to disable HMR as a workaround for now.

[krpatter-intc]

Searching the code I found the --no-hmr parameter after your hint (thanks!), and I can confirm that running with --no-hmr works