-
Notifications
You must be signed in to change notification settings - Fork 8
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
Dependencies are always built with exact version contraints #271
Comments
Do you have an example reproduction for this? And which language are you experiencing this with? The version ranges specified in the original library should be retained... |
I've observed this in c#, but I believe it applies to all languages. The reason is https://github.com/aws/jsii-srcmak/blob/5d14a0ce15a79e578ab01d5a16c8de59bc049229/src/compile.ts#L40 which is reading directly from the installed dependency module. Not a simple example, but you can see it happening here: Source package: https://github.com/terraform-cdk-providers/cdktf-provider-project/blob/8619150f4468bfa7949344879dae5fa5431b7998/src/cdktf-config.ts#L19 |
This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. |
Closing this issue as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
@RomainMuller can we reopen this and remove the |
This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label. |
Closing this issue as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. If you wish to exclude this issue from being marked as stale, add the "backlog" label. |
Any dependencies are passed to jsii by reading the version out of the module's
package.json
file. This results in an exact version being required. This makes it more difficult to use the generated code with other libraries which may use a different version of the dependency.Changing
Options.dep
to{ [module: string]: string }
would allow specifying a SemVar version for each module dependency. Could instead add a new option or union type to maintain compatibility.The text was updated successfully, but these errors were encountered: