-
Notifications
You must be signed in to change notification settings - Fork 52
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
Webpack declares alias of "itkConfig.js" but is not referenced. #822
Comments
Hello! In recent versions of itk-wasm WebPack alias for |
Thanks for your solution ! Then, do I have to call all other settings (imageIO, meshIO ...) by method like "pipelineWorkerUrl"? And is there a separate page that provides information about these initial configuration settings? |
Currently these are still overridden by itkConfig.js, but they will not need to be set separately from pipelinesBaseUrl.
The documentation will be updated after image-io, mesh-io migration is complete. To summarize for each package (image-io and mesh-io are migrating to their own package per #716 ), the configuration setting will be:
|
I will refer to it when updating the latest version of itk-wasm. First of all, there seems to be a conflict in my current project environment, so if I fix it, I will write the cause. Thank you ! |
I found a solution to my problem. In my project, I excluded node_modules in the "babel-loader" setting. Accordingly, I changed itkConfig.js to common.js form. In addition, the '@babel/plugin-transform-modules-commonjs' plugin was setup to have the process of transform the ESM to common.js. |
Hello !
I'm trying to use itk-wasm, but I found that
ServiceWorker
is not being created.I suspect that the reason I identified is that the webpack alias of
itkConfig.js
I declared is not reflected.In
createWebWorkerPromise.js
, the config is treated as undefined and returns an error.Is there any data to refer to or possible cause in this regard?
Thank you.
The text was updated successfully, but these errors were encountered: