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

multiple vs single unstable module #281

Closed
wants to merge 3 commits into from

Conversation

NetaNir
Copy link
Contributor

@NetaNir NetaNir commented Jan 11, 2021

This PR is not meant to be merged, it is only meant to allow us to separately discuss one aspect of the V2 Experiments RFC.


By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache-2.0 license

@NetaNir NetaNir added the pr/do-not-merge Let mergify know not to auto merge label Jan 11, 2021
text/alpha-modules.md Show resolved Hide resolved
The advantages of vending as separate modules:

1. The same experience as any other 3rd party library.
2. Easier for 3rd parties to contribute modules, which we can first incubate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure i understand this point


We know from our current dependency tree, that unstable modules depending on
other unstable modules is a valid use case. From the 35 unstable modules we
currently have, ~3 of them depends on other unstable modules.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which ones? It's important to understand the nature of the dependency

`peerDependencies`.

The main concern raised in the PR was that doing so will result in "the same
dependency hell monocdk was meant to solve". As commented on the PR, this is not
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This also brings up again the fact that those will be exactly like any 3rd party module in the ecosystem so if we have an issue it applies to the entire ecosystem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/do-not-merge Let mergify know not to auto merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants