Meteor 1.5 update: imports server error on build

help
1

Just updated to 1.5. Got the following issue immediately:

=> Started proxy.                                                                        
/Users/<user>/.meteor/packages/coffeescript/.1.12.3_1.ph1kh6++os+web.browser+web.cord
ova/plugin.compileCoffeescript.os/npm/node_modules/meteor/promise/node_modules/meteor-pro
mise/promise_server.js:190                                                               
      throw error;                                                                       
      ^                                                                                  

TypeError: Path must be a string. Received undefined                                     
    at assertPath (path.js:8:11)                                                         
    at Object.posix.relative (path.js:496:3)
…

Also here is package list:

meteor-base@1.1.0             # Packages every Meteor app needs to have
mobile-experience@1.0.4       # Packages for a great mobile UX
mongo@1.1.18                   # The database Meteor supports right now
blaze-html-templates@1.0.4 # Compile .html files into Meteor Blaze views
reactive-var@1.0.11            # Reactive variable for tracker
tracker@1.1.3                 # Meteor's client-side reactive programming library

standard-minifier-css@1.3.4   # CSS minifier run for production mode
standard-minifier-js@2.1.0    # JS minifier run for production mode
es5-shim@4.6.15                # ECMAScript 5 compatibility for older browsers.
ecmascript@0.8.0              # Enable ECMAScript2015+ syntax in app code
shell-server@0.2.3            # Server-side component of the `meteor shell` command

random@1.0.10
check@1.2.5
reactive-dict@1.1.9
session@1.1.7
aldeed:collection2-core
aldeed:template-extension
kadira:flow-router
kadira:blaze-layout
arillo:flow-router-helpers
gwendall:body-events
msavin:mongol
fourseven:scss
coursierprive:tether
aldeed:autoform
accounts-password@1.3.6
alanning:roles
coffeescript
http@1.2.12
email@1.2.1
froatsnook:sleep
okgrow:analytics
simple:reactive-method
cosio55:autoform-cloudinary
dynamic-import

Exploring options for fixes… will update here.

2

im having the same error after update to 1.5

3

Ok good to know. I’m removing any unused/non-crucial packages to try and narrow the field. The error to me would most likely come from changes to imports with dynamic-import(?)

4

Have removed these packages without improvement (still same error)
dynamic-import
simple:reactive-method
froatsnook:sleep

5

I have the same problem after upgrade to 1.5

I have tried resetting everything:

  • rm -fR ~/.meteor
  • rm -fR <project>/node_modules
  • meteor update
  • meteor npm install

nothing changed.

btw. I think the thread title is a bit misleading. The error doesn’t have anything to do with promises. It is an import with processing imports

6

Thanks, updated title.

7

I have fixed the symptom on my end.
In my case the problem was connected to okgrow:analytics package.
Removing it fixed the problem, but I guess it’s a more involved issue with the recent changes to how imports/babel works.
Here is an issue I have raised with the okgrow team.

YMMV - try the method I have used in the link above to track down the package that your build is failing at…

PS. Still the title - it doesn’t have anything to do with promises… The promise mentions you see in the stack trace is just a product of how the importing is implemented in meteor.

8

Can confirm meteor remove okgrow:analytics does solve the problem. Will track the issue on github.

Also further refined title of this thread.

1 Like
9

Does anyone know what the core issue causing this turned out to be? I’m experiencing this with one of my packages and have spent forever on this to no avail.

10

The thing that fixed this for me was doing a hard delete on my ~/.meteor folder and reinstalling meteor from the website. From there I re-upgraded my project (after doing a git reset on my repo) by specifying meteor update --release 1.5. I have not tried for 1.5.1.

1 Like
11

Not sure the exact cause on my end but it turns out deleting the node_modules folder from within the package fixed this.