Momo Kornher

Okay it seems like we never changed the default linker in `yarnBerryOptions` to be `"node-modules"`

Yes, the python package and the Node.js package are independent of each other. Your `.projenrc.py` file will be using the python package. I'm not actively using projen with python, so...

FWIW, this is valid YAML because any JSON is valid YAML. ``` # ~~ Generated by projen. To modify, edit .projenrc.ts and run "npx projen". {} ```

Hmm. I'll need to check this, it doesn't feel like intentional behaviour but I'm not sure. The alternative is to run `pipx run projen new`. This isn't well documented at...

Moving forward, I think we need to change the default setting for the linker. @blimmer what do you think ?

I cannot reproduce this with either `pipx` or `npx projen`: ```console $ pipx run projen new python --poetry $ cat package.json cat: package.json: No such file or directory ``` ```console...

Fundamentally I think projen's concept of providing an `env` for task to run in, is reaching its limits now. With Yarn PNP, the only way to run scripts properly seems...

Or I suppose we could state that `projen` the task runner is not compatible with Yarn PnP and one must use Yarn as task runner in this case.

I can't imagine that's the cause. `package.json` is only created by a `NodeProject` to my knowledge, or specifically by the `NodePackage` component. How does the `package.json` file look? Did you...

> How about just using `yarn exec` in the task definitions when `packageManager` is `NodePackageManager.YARN_BERRY`? > > This would also serve to self-document working in the same "style" as the...