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

"meteor npm list -g" not working on windows (looking in wrong directory) #7508

Closed
brucejo75 opened this Issue Jul 27, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@brucejo75
Copy link
Contributor

commented Jul 27, 2016

Observed

On Windows run meteor npm list -g command:

meteor npm list -g
C:\Users\<username>\AppData\Local\.meteor\packages\meteor-tool\1.4.0\mt-os.windows.x86_32\dev_bundle\bin
`-- (empty)

Expected

List of node modules found here:C:\Users\<username>\AppData\Local\.meteor\packages\meteor-tool\1.4.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules

Looks like the command is looking in the wrong directory.

This is windows only, seems to work fine on my MacOS install.

Version info

  • Windows 10.10586.494
  • Meteor: 1.4
  • Meteor npm: 3.10.5
  • Meteor node: v4.4.7
@abernix

This comment has been minimized.

Copy link
Member

commented Jul 28, 2016

I don't think the global NPM scope of the Meteor bundled npm has really been considered before. The inconsistency between Windows and Linux is bizarre, but what do you need out of this functionality?

In a way, giving users access to the correct Meteor "global" directory and user's willingness to copy and paste whatever examples they come across (which might install into the global scope) leaves possibility for users to break core functionality of their meteor tool by doing meteor npm install -g package@incompatible-version.

@brucejo75

This comment has been minimized.

Copy link
Contributor Author

commented Jul 28, 2016

Interesting point @abernix.

  • using meteor npm install -g was an attempt to understand what packages were in my dev_bundle
  • overall I am struggling with how to think about the meteor global repository in the dev bundle.

If you do not want people to execute this command, it is weird for it to work on MacOS (linux) and not work on Windows. Would you prefer to disable it overall? I think it might be simpler to simply make it work.

And I think it may be worthwhile to write up an explanation of the dev_bundle and how you expect users to think about it.

I have been confused about the different repositories and I posted my perspective on it in the forums.

Would you mind taking a few minutes and clarifying the meteor perspective? Are my assumptions correct? Is there more to consider?

Thanks!

@hwillson

This comment has been minimized.

Copy link
Member

commented Feb 2, 2017

While it is definitely a bit annoying this works on MacOS but not windows, I think we're okay to close this issue for now since:

  • Using the global scope of the Meteor bundled npm isn't something that developers should have to do.
  • If anyone runs into this issue in the future, the discussion here (and in the forums) documents it fairly well.
  • The chances of anyone working on addressing this issue are quite low, since this isn't really a feature that Meteor devs should need to worry about.

Thanks very much for opening this issue originally!

@hwillson hwillson closed this Feb 2, 2017

@abernix

This comment has been minimized.

Copy link
Member

commented Feb 7, 2017

See also #8277, as it sounds related (still open and being debugged).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.