fix `npm install -g ferment` version mismatch error #5

Closed
mmckegg opened this Issue Oct 5, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@mmckegg
Collaborator

mmckegg commented Oct 5, 2016

For some reason #2 hasn't fixed npm install -g ferment.

@ahdinosaur @mixmix Any ideas how to solve this?

mmckegg added a commit that referenced this issue Oct 5, 2016

mmckegg added a commit that referenced this issue Oct 5, 2016

@mmckegg

This comment has been minimized.

Show comment
Hide comment
@mmckegg

mmckegg Oct 5, 2016

Collaborator

@ungoldman Just tried using postinstall but while it runs, doesn't actually seem to be triggering a rebuild. You still get the error.

This probably would have worked with the old nested node_modules, but I suspect is having trouble with the flat structure.

Edit: Actually just researched global installs, and while it still uses the flat structure, it actually puts all of the modules for that particular package inside package/node_modules. So it probably isn't the reason for the problem.

Collaborator

mmckegg commented Oct 5, 2016

@ungoldman Just tried using postinstall but while it runs, doesn't actually seem to be triggering a rebuild. You still get the error.

This probably would have worked with the old nested node_modules, but I suspect is having trouble with the flat structure.

Edit: Actually just researched global installs, and while it still uses the flat structure, it actually puts all of the modules for that particular package inside package/node_modules. So it probably isn't the reason for the problem.

@arj03

This comment has been minimized.

Show comment
Hide comment
@arj03

arj03 Oct 5, 2016

I can confirm that the 0.2.2 rebuild option works :)

arj03 commented Oct 5, 2016

I can confirm that the 0.2.2 rebuild option works :)

@mmckegg

This comment has been minimized.

Show comment
Hide comment
@mmckegg

mmckegg Oct 5, 2016

Collaborator

Awesome, that's great! Thanks letting me know 😅

Collaborator

mmckegg commented Oct 5, 2016

Awesome, that's great! Thanks letting me know 😅

@Marak

This comment has been minimized.

Show comment
Hide comment
@Marak

Marak Jul 31, 2017

Contributor

Closing.

Most likely was issue with npm cache / older versions of npm.

If anyone hits this issue again please make sure to update npm CLI to the latest version and try running npm cache clean

Contributor

Marak commented Jul 31, 2017

Closing.

Most likely was issue with npm cache / older versions of npm.

If anyone hits this issue again please make sure to update npm CLI to the latest version and try running npm cache clean

@Marak Marak closed this Jul 31, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment