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
Allow specifying location of pnpmfile.js
in the package.json
.
#910
Comments
|
actually, my suggestion would be to use npm's config-system instead of the field in If this will be a npm config, it will be a lot more powerful. It will allow specifying globally one |
I prefer a |
sure, but you can have a |
Ah, didn't know about |
I find this an overkill and a feature creep, at least for the reasons mentioned. Firstly, who does that? As in where did you see this pattern? Secondly, why is it so much harder to Thirdly, just like I was mentioning in another pnpm thread that it is a bad idea to pollute package.json with new configuration keys, it si also a bad idea to pollute .npmrc . AFAIC both are owned by npm and npm alone. |
Why use folders to organize your source code...why not keep everything flat file ;) Monorepos. Cleaner github.com/foo/bar homepage. Less vertical space in tree view in IDE/text editor. Many reasons.
I create tons of packages in monorepos so I prefer having as few files as possible per package. I would rather have all config in one file, but am forced not to because of every tool maker defining a different naming standard and hard-coded location.
If you were creating config for your project, you would not use 10 different file naming standards, and keep everything in the root folder. But you are forced to atm. |
I vote for Consider this situation as a reason for supporting the feature:
In this situation it is:
Having a global file will alleviate the whole situation. |
So it will be possible to do |
That will be fantastic, but are you saying this will not be supported:
|
Only one |
🚢 1.39.0 |
There are already so many files cluttering the project root.
Would be cool if the location of
pnpmfile.js
could be configured in thepackage.json
.Use case: I want to put it in
tools/pnpmfile.js
, so I can easily copy thetools
folder to other projects as a kind of project boilerplate.The text was updated successfully, but these errors were encountered: