Momo Kornher
Momo Kornher
@Butterneck You can see the difference here https://github.com/mrgrain/projen-cdk-construct-test/compare/5023db9...89d5d78 (make sure to load the diff for all generated files). But basically the release GitHub Actions workflow will do more than just...
> I don't think so, projen re-synthesize the package.json every time I run it, overriding any manual edit. Okay, then the other is to tag the current commit with the...
@Butterneck Documentation improvements aside, are you all good now are still having issues with the versioning?
Closing for now with the updated docs. There is a good argument to have `package.json` track the current version, but it comes with implication. We should discuss this in a...
`@aws-sdk` v3 is currently not compatible with jsii due to a dependency on TS 3.9 Fix will depend on https://github.com/aws/aws-cdk-rfcs/pull/373
Works as designed by jsii. Feel free to open an issue/discussion at [aws/jsii](https://github.com/aws/jsii).
I think the best way would be to write the command in JS/TS/Python/etc. There's no easy way to configure projen for that, but something like `project.addTask('node hello-world.js');` should work.
Local linking of CDK constuct to app experience is not optiman due static devDependencies versioning
Running `projen build` and referring to the bundled output is the recommended way at the moment. In general, I think this is an issue with package managers.
`publishConfig` is kind of a Quality of Life setting which is less relevant in an automated release workflow like `projen` provides. I guess one way to look at it is...
I'm not disagreeing with you at all. `npmDistTag` is currently tightly coupled to the built-in release mechanism. It would have been more clear to users, if the option would be...