-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[ui] Namespaced and file-specified deps for consul-ui #21378
Conversation
Awesome work @philrenaud, thanks a lot for doing that this quickly 🙌 |
4007e05
to
e18b631
Compare
Note: in order to resolve a non-standard license in a dependency-of-dependency-of-dependency, in 36fef17e6cdc9dbb088de1bbad9bc4ed44eee6ee I've done two things:
|
ee4cc11
to
7277670
Compare
a2e4715
to
79d8b85
Compare
…ackages to come from npmjs
79d8b85
to
8d13103
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Huge thanks for fixing this and for all the details you have provided for the resolution, it's awesome 👍
We can merge once tests are passing
* Namespaced and file-specified deps * Pinning to a specific version of tailwind and setting config for js packages to come from npmjs * Pin glob instead of reverting tailwind or any other (grand)parent dependency * ember-cli-build fixed path resolution for now-namespaced submodules * Dropping the namespace prefix and relying on relative pathing
Description
This resolves an ambiguous dependency resolution in consul-ui in the event that a developer attempted to
yarn install
ornpm install
from a non-workspace-root directory. This handles it in two ways:@hashicorp/
prefix, reducing the risk of a hypothetical public registry squat situation should local packages ever stop being relativeSomething to note with this is that the packages become a little more bound together than before; for example, it would be more difficult to maintain multiple valid versions of a sub-package here and let
consul-ui
differentiate between them. We could expand this into submodules some day, but not today.