feat: read the workspace project location globs from package.json

[zkochan]

Related discussion: #3205

[shellscape]

Generally not in favor of this citing my comment #3205 (comment). There are two camps here: those who want package.json to contain every bit of config for the workspace and willing to pollute the hell out of the file, and those who prefer many files with distinct intent. I'm strongly in favor of separation of concerns and putting as little in package.json as possible. Perhaps if package.yaml was a thing I wouldn't feel so strongly, but JSON is not a good configuration language, and package.json was never meant to contain anything but metadata for NPM packages.

This is a great example of "just because yarn did something, doesn't mean we should."

[zkochan]

Closing for now. Maybe the warning that I added via #5547 will be enough.

[liujiayii]

But now it is the standard of npm, It's not just yarn
.

[shellscape]

I don't think that's a convincing argument. this project was created to counter the deficiencies in NPM. they've historically made very poor decisions, and using them as a source of truth has never really been wise

[juanpicado]

I could not more agree with @shellscape , already we can see the side effects of polluted package.json, even with almost no using many external metadata at the package.json some practices are leading to this, I've seen many projects doing this more often if we the package manager encourage this at the end users might pay the price eventually npm/feedback#765 (comment)