[SOLVED] Error with npm install worker_threads

[bmcgonag1]

Suddenly when i run the meteor command (without having updated meteor, or anything) I get the message on both my mac and linux machines saying worker_threads may be needed, and if so run

meteor npm install --save worker_threads

If I just ignore it, my localhost:3000 server starts, but when I try to load the page, it gives a bunch of errors in the chrome console about worker_threads.

If I run the command above, it fails with a 404 error. What’s happening here?

[bmcgonag1]

Is no one else seeing this?

[bmcgonag1]

I feel like an idiot.

So, I like Visual Studio Code because it tries to save you some work, right. Well, it tried to save me some work by adding an import for the threaded option of worker_threads apparently…which I don’t need, didn’t want, but I guess typed something that made it think I needed that.

Removed that erroneous import line once I spotted it, and all is good again…ugh.

[tathagatbanerjee]

So i’m seeing the same issue, mine looks like so:

q6a@1.0.2 start /home/tbanerjee/workspace/meteor/app1
> meteor --settings settings-development.json

[[[[[ ~/workspace/meteor/app1 ]]]]]           

=> Started proxy.                             
                                              
Unable to resolve some modules:

  "worker_threads" in                         
/home/tbanerjee/workspace/meteor/app1/node_modules/write-file-atomic/index.js
(web.browser)
                                              
If you notice problems related to these missing modules, consider running:
                                              
  meteor npm install --save worker_threads    
                                              
                                              
Unable to resolve some modules:

  "worker_threads" in                         
/home/tbanerjee/workspace/meteor/app1/node_modules/write-file-atomic/index.js
(web.browser.legacy)
                                              
If you notice problems related to these missing modules, consider running:
                                              
  meteor npm install --save worker_threads    
                                              
=> Started MongoDB.                           
I20190424-10:19:16.193(10)? Kadira: completed instrumenting the app
I20190424-10:19:16.378(10) (migrations_server.js:80) Migrations: Not migrating, already at version 1
=> Started your app.

=> App running at: http://localhost:3000/

As said above, it does not cause any problems per se, but looks ugly. Its a warning that comes from there being a lack of an --experimental flag in node, and will be resolved post node 11.7 (the warning no longer shows), so Meteor 1.9 presumably (node12) will fix this.

Not sure about above, mostly based of googling. If anyone knows any more, be most appreciated.