Database not initializing properly #296
Replies: 5 comments 5 replies
-
I'm having the same issue. For me, while working without a web worker via workerInjector it gives
I can't upgrade the version post 4.3.10 due to this. 4.4.0 and above gives error. I have a Webpack 4 configurated React app that was perfectly running with JsStore 4.3.9 (4.3.10 also works fine), then decided to upgrade to 4.4.4 but had When I import "workerInjector" to use JsStore without web worker, I can see that Webpack is doing its job to import the module. Because when I console.log it, I see the printed workerInjector variable.
I assume the problem occurred after the changes to the library related to compression or Webpack 5. Any ideas? @ujjwalguptaofficial |
Beta Was this translation helpful? Give feedback.
-
yeah it must be broken after upgrading to webpack5. Will try to reproduce and fix ASAP. |
Beta Was this translation helpful? Give feedback.
-
@AceIsHuman @alisabrigok issue has been fixed in v - 4.4.5. Please install and let me know. The issue got introduced due to webpack upgrade, i have also added some test cases - so that it don't ger reproduced again. |
Beta Was this translation helpful? Give feedback.
-
I just installed version 4.4.5 and it fixed my issue. Thanks for the swift replies and fixes @ujjwalguptaofficial |
Beta Was this translation helpful? Give feedback.
-
Just updated to 4.4.5 and the issue seems to be fixed for I cannot get the database to initialize with a web worker. The following code does not produce an error, it just gets hung up on line 5 at
I have also tried creating a preload script in place of the import on line 2. This produces the same result.
|
Beta Was this translation helpful? Give feedback.
-
Creating a database with and without a web worker causes errors like
this.worker_.postMessage is not a function
andworkerRef.queryManager is not a constructor
.Node v16.17.1
Electron v20.3.0
Vue 2.6.12
Jsstore did previously work on node v14.20.0. Could this be an issue related to Node, and is there any possible workaround while using v16.17.1?
Beta Was this translation helpful? Give feedback.
All reactions