guillaumeduboc

@Nyugue we have simplified the CI now and this issue shouldn't happen anymore ! you can look at it if you want to update yours

Now that we have only one job for the build and run we won't lose precious time between our steps. But we might have a mismatch of cache between 2...

In fact I believe there shouldn't be any mismatch - For `yarn` or `pnpm`, the lockfile is cached and shouldn't change even if `syncpack format` changes the `package.json` - For...

I've been looking into this issue, and the top level await works great ! Indeed we cannot `import ... from 'aws-sdk'` in a lambda, because the library cannot be resolved....

Hey @btd, I looked into simply copying the PR to the rollup plugin but I think it won't be sufficient. It seems the tree built from the esbuild and rollup...

Here is the `outputBundle` for the rollup plugin [output-bundle.json](https://github.com/btd/rollup-plugin-visualizer/files/13539977/output-bundle.json) you can see that there is no `moduleId` for the `/user/rollup-plugin-visualizer/node_modules/d3-hierarchy/src/index.js` file but `/user/rollup-plugin-visualizer/src/treemap/index.tsx` specifies it in its `importedIds` (in the...

I believe it is ok to use `anyOf` with `additionalProperties: false`. We don't necessarily want overlapping subschemas to fail have you tried @Sc0ra ?

I've been looking into this these past days First of all thanks for the repro example and the `--no-save` for pnpm ! I have a working pr #26770 but I...

Hey @fwang I saw that so fare the interface has been the `cdk` prop I must say that in my use case I'd really like to be able to reuse...

My bad, I didn't understand what you meant you are right, for the bucket it doesn't change much. And I think this is a great interface for a stateful resource...