Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web Worker support for Dojo 2 Applications #190

Open
maier49 opened this issue Jun 29, 2017 · 1 comment
Open

Web Worker support for Dojo 2 Applications #190

maier49 opened this issue Jun 29, 2017 · 1 comment
Assignees

Comments

@maier49
Copy link
Contributor

maier49 commented Jun 29, 2017

Dojo 2 Applications should support the use of Web Workers where they are available with some sort of fallback to ensure the application is still isomorphic.

The worker-loader allow with a call to require(worker-loader?....), but we want to avoid inline usage of loaders.

Kit:

Also, if we do go with an approach like this, we should still find a better way to integrate it. We can type plugins now with something like:

declare module 'worker-loader?*' {
  export = /* ... */
}

Would we not be able to create something that wrapped ES import() that we could also inject some feature detection, so the code was isomorphic on Node.js as well?

@agubler
Copy link
Member

agubler commented Jul 5, 2017

Do you think that we could use worker-loader but not inline? and perhaps introduce a convention for web workers, maybe *.worker.ts and/or allow consumers to register specific worker files via the .dojorc?

module: {
	rules: [
		{
			test: /\worker.ts$/,
			loader: 'worker-loader'
		}
	]
}

@kitsonk kitsonk added the beta3 label Jul 27, 2017
@dylans dylans modified the milestones: 2017.07, 2017.08 Jul 29, 2017
@kitsonk kitsonk modified the milestones: 2017.08, 2017.09 Sep 4, 2017
@dylans dylans modified the milestones: 2017.09, 2017.10 Oct 10, 2017
@kitsonk kitsonk removed the beta3 label Oct 30, 2017
@kitsonk kitsonk removed this from the 2017.10 milestone Oct 30, 2017
@kitsonk kitsonk added this to the beta.4 milestone Oct 30, 2017
@kitsonk kitsonk added beta5 and removed beta4 labels Dec 1, 2017
@kitsonk kitsonk modified the milestones: beta.4, beta.5 Dec 1, 2017
@agubler agubler removed the beta5 label Jan 4, 2018
@agubler agubler removed this from the beta.5 milestone Jan 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants