[solved] Cannot find module '@babel/runtime/helpers/builtin/objectSpread' after update meteor to 1.6.1.1

help
4

Thank god we have people like @robfallows!

6 Likes
5

+1 @robfallows you’re a godsend, thank you

2 Likes
6

Godspeed, @robfallows. Saved me countless hours and a few headaches. If you ever need a beer send me your venmo.

7

After upgrading 1.7, getting below error unfortunately can’t get rid of by installing @babel/runtime via npm


W20180804-15:20:47.159(3)? (STDERR) D:\Work\nosqlclient\.meteor\local\build\programs\server\boot.js:475
W20180804-15:20:47.258(3)? (STDERR) }).run();
W20180804-15:20:47.258(3)? (STDERR)    ^
W20180804-15:20:47.259(3)? (STDERR) 
W20180804-15:20:47.259(3)? (STDERR) Error: Cannot find module '@babel/runtime/helpers/builtin/interopRequireDefault'
W20180804-15:20:47.259(3)? (STDERR)     at Function.Module._resolveFilename (module.js:547:15)
W20180804-15:20:47.259(3)? (STDERR)     at Function.resolve (internal/module.js:18:19)
W20180804-15:20:47.260(3)? (STDERR)     at Object.require (D:\Work\nosqlclient\.meteor\local\build\programs\server\boot.js:288:32)
W20180804-15:20:47.260(3)? (STDERR)     at makeInstallerOptions.fallback (packages\modules-runtime.js:604:18)
W20180804-15:20:47.260(3)? (STDERR)     at Module.require (packages\modules-runtime.js:230:14)
W20180804-15:20:47.260(3)? (STDERR)     at require (packages\modules-runtime.js:244:21)
W20180804-15:20:47.261(3)? (STDERR)     at livedata_connection.js (D:\Work\nosqlclient\.meteor\local\build\programs\server\packages\ddp-client.js:147:30)
W20180804-15:20:47.261(3)? (STDERR)     at fileEvaluate (packages\modules-runtime.js:322:7)
W20180804-15:20:47.261(3)? (STDERR)     at Module.require (packages\modules-runtime.js:224:14)
W20180804-15:20:47.261(3)? (STDERR)     at require (packages\modules-runtime.js:244:21)
8

running meteor npm install @babel/runtime@latest
didn’t solve the problem for me

9

Keep your @babel/runtime version at 7.0.0-beta.55

The latest version of 7.0.0-beta.56 has a breaking change that is only fixed at Meteor 1.7.1-beta.27

10 Likes
10

I am having this problem when I am tring to run the app. meteor npm install @babel/runtime@latest did not worked.

11

This may sound unfriendly: But did you read all the posts in this topic?

12

I tried that but it is not working. My previous project is working fine with version 42. Error: Cannot find module @babel/runtime/helpers/builtin/interopRequireDefault. Any other solution?

13

According to @rjdavid’s answer, meteor npm install @babel/runtime@7.0.0-beta.55 does work.

2 Likes
14

yup… this worked for me. Was following tutorial and boom… did not get very far.

meteor npm install @babel/runtime@7.0.0-beta.55

3 Likes
15

or simply remove the caret ^ in package.json and thus pin it to a specific version.

4 Likes
16

As some one who is new I had no idea I could simply make a change the package file and fix the issue…

Thanks!

1 Like
17

You know I love the Meteor framework but there needs to be a better job at testing and communicating with their user base.

I just got a new Mac because I want to build apps for iOS devices. So I install meteor, create a meteor app and run meteor as described in the instructions. And I get this @babel/runtime error.

There has to be a way to communicate better to us. And BTW yes @robfollows is the man. He has saved me more than once.

1 Like
18

In fairness to Meteor, the breaking changes happened outside of Meteor e.g. an npm package. Checking the releases now, they are preparing the release of 1.7.0.4 (in rc.1) to handle the breaking changes brought by the babel package.

1 Like
19

this work for me also, thanks!
just run:

meteor npm install @babel/runtime@7.0.0-beta.55
12 Likes
20

This worked for me, thank you!

1 Like
21

Yeah well… I love Meteor, but they never should have migrated to the babel 7 beta releases. Babel is causing troubles ever since.

Yes, babel is causing the issues. But it’s MDG who decided that building upon the beta’s was a good idea.

1 Like
22

Thank you @rjdavid - this worked for me!

23

Just encountered this error because I had a git repo EXPLICITLY setting .meteor/release as a METEOR@1.9 project.

I had created a new meteor project and brought my files in, which was created as 1.10.1.

Install is fine, boot is fine, but my code then kind of downgrades the project and pukes.

Changed my version to match and it booted right up. Scary.

1 Like