-
Notifications
You must be signed in to change notification settings - Fork 767
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
new build 0.10.0 version is not working inside web workers #818
Comments
ChaosEngine
added a commit
to ChaosEngine/Dotnet-Playground
that referenced
this issue
Sep 19, 2020
… bootstrap-table; Internal fix for digitalbazaar/forge#818 (new build 0.10.0 version is not working inside web workers)
ChaosEngine
added a commit
to ChaosEngine/Dotnet-Playground
that referenced
this issue
Sep 19, 2020
… bootstrap-table; Internal fix for digitalbazaar/forge#818 (new build 0.10.0 version is not working inside web workers)
on worker side, adding below seems to resolve problem: |
@ChaosEngine That actually worked. Thanks |
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably due to new webpack default settings outputglobalobject which is
window
we are seeing this generated inside forge.all.min.,js and forge.min.js now(window, (function () {
and previously we had this
"undefined"!=typeof self?self:this
which allowed to run node-forge inside web workers.
Possible solution? Apply this to
webpack.config.js
The text was updated successfully, but these errors were encountered: