Zach Tindall

For those using TypeORM, using the `Relation` type resolved the issue for me https://typeorm.io/#relations-in-esm-projects

I can work on this as I also need this feature. However, this feature is still in beta and is not supported by the v1 api endpoints. Once the v2...

I had to run the command by disabling plugins to get a new app created ``` NX_ADD_PLUGINS=false yarn exec nx g app my-app --bundler webpack --e2eTestRunner none --directory apps/my-app --verbose...

Created https://github.com/nrwl/nx/issues/26245 for the issue with the jest plugin

@draylegend you may want to look at the solution here: https://github.com/nrwl/nx/issues/26556#issuecomment-2195041213 I had to add an empty `options` object to the plugins listed in the nx.json

@draylegend, look like your issue is different. You already have an `options` object in both plugins ``` "plugins": [ { "plugin": "@nx/playwright/plugin", "options": { "targetName": "e2e" } }, { "plugin":...

This happens with and without custom plugins listed in the nx.json

@AgentEnder, any thoughts on a workaround to this one?

Same with 19.3.1. Updated the repo with the latest version

Turns out that the `options` object is now required (or the plugins are not checking for it's existence before accessing it's properties). Adding an empty `options` object to each plugin...