Mitchell Valine
Mitchell Valine
I think its purely performance
added `pr/do-not-merge` after discussing possible breakage when an existing construct library depends on a package that then will be generated with the new python code gen. We only explicitly built...
@mattsb42-aws to clarify this occurs only when using a file path as the dependency version in package.json, but `npm link`ing works okay right? I think we mostly link in our...
@mbonig Thanks for the report. You have your current jsii version as `6.13.6` which doesn't exist. Assuming you're experiencing this on the current release, `0.22.0`. Is that correct?
Yeah something is funny here. Might be a Windows specific issue. Will dig in a bit more.
oooh interesting. I wonder if a similar fix can be found for @mbonig's issue. I've always relied on the `old and busted` for referencing local packages. @mbonig if you clean...
Yeah this should be doable to embed in the module entrypoint or as a separate file but the same `package` as the root package in the module.
@RomainMuller but this is purely a naming collision right? We can make the sub-package something obscure and worst case scenario a user can alias it or another package if needed...
We have been talking about this for awhile and is something we are actively exploring now!
construct hub fails to display non-typescript documentation for libraries with compressed assemblies
Looks like this is resolved now that #959 is merged.