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

Ensure @node/types is available #251

Closed
wants to merge 2 commits into from

Conversation

fearthecowboy
Copy link

I cloned this and used PNPM instead of NPM and it doesn't find @node/types because it's not a devDependency.

(I assume it's installed as a dependency of something else, but PNPM isn't as lax as NPM when it installs things. )

  • adds @node/types

@eemeli
Copy link
Owner

eemeli commented Mar 29, 2021

That's rather surprising. I just did a fresh clone of the master branch, and at least for me pnpm it and pnpm run test:types succeed without any issue, and the transitive @types/node dependency does show up in node_modules.

Could you add instructions for reaching the error case that prompted this PR?

@eemeli eemeli added the need more info More information is required in order to replicate and identify the reported issue label Mar 29, 2021
@fearthecowboy
Copy link
Author

Oh, my apologies. I assumed it was PNPM.

My case had me adding your repo as a submodule to my monorepo project (managed with @microsoft/rush )
I guess then it's rush doing that.

(ah yes, I see that's what caused it. Hmm. I thought it was PNPM that was pedantic about that, turns out it's rush. )

Oh, and you're using * instead of a specific version.

@eemeli eemeli closed this in 64dc1e0 Apr 1, 2021
@eemeli
Copy link
Owner

eemeli commented Apr 1, 2021

Even though this smells like it might be a @microsoft/rush bug, there are a few places in the sources that do admittedly refer to Node.js types, so adding the dev dependency is valid. Done now, including an update to the lockfile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need more info More information is required in order to replicate and identify the reported issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants