Skip to content
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

Unable to resolve some modules: spawn-sync #231

Open
RobinVanCauter opened this issue Nov 18, 2016 · 3 comments
Open

Unable to resolve some modules: spawn-sync #231

RobinVanCauter opened this issue Nov 18, 2016 · 3 comments

Comments

@RobinVanCauter
Copy link

RobinVanCauter commented Nov 18, 2016

I'm running Meteor 1.4.2.3 with fourseven:scss v3.10.1 and everytime my application runs I get the following error:

Unable to resolve some modules:

  "spawn-sync" in /home/robin/moonkin/bazaar/orbiter/node_modules/cross-spawn/index.js (web.browser)
                                              
If you notice problems related to these missing modules, consider running:
                                              
  meteor npm install --save spawn-sync

Running the advised command doesn't change anything. As far as I know it's node-scss that depends on this package (or whatever the package fourseven:scss depends on is called exactly).

Any ideas on how I could fix this?

@RobinVanCauter RobinVanCauter changed the title Unable to resolve some modules: span-sync Unable to resolve some modules: spawn-sync Nov 18, 2016
@MeteorStartup
Copy link

i got same issue,
but I didn't follow up that advise cause it's not clear.

Any idea?

@sebakerckhof
Copy link
Collaborator

Can you retry with Meteor 1.4.2.7+ and latest fourseven:scss

@s7dhansh
Copy link
Contributor

s7dhansh commented Jun 8, 2018

Still getting the same issue. Had ignored it for long, until today, and saw this issue open.
Meteor 1.7, fourseven:scss updated.

Edit:
In my case it was not caused by fourseven:scss. It was caused because of gm being imported on the client accidentally. After removing that, everything's perfect now. gm has a dependency on cross-spawn which in turn depend on spawn-sync, but probably that dependency is marked as serverOnly, causing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants