NullVoxPopuli
NullVoxPopuli
what sub-project is throwing the error?
Does the same behavior happen when you do `pnpx ember-cli@latest new my-app --pnpm`?
is `@babel/plugin-proposal-decorators` declared in your test-app's package.json?
What happens if you add that to the root package.json?
This also feels like a bug in the VSCode editor extension for eslint :thinking:
I think this is, in general, resolved. I generated a new project, ```bash npx ember-cli@latest addon test-eslint --blueprint @embroider/addon-blueprint --pnpm cd test-eslint ``` and then opened vscode, typed some gibberish,...
I think we're blocked on ember-data not being compatible with the stable types. Everyone is free to delete all the `@types/` packages in favor of the stable built in types...
hello! do you have a reproduction of this I could look at? rollup shouldn't be running :sweat_smile:
yeah, I think we can add `ember-source` and `@glimmer/component` right away.
on a non-typecript project, I get these errors: ``` WARN Issues with peer dependencies found peer-test ├─┬ ember-source 4.10.0 │ └─┬ ember-auto-import 2.5.0 │ ├─┬ babel-loader 8.3.0 │ │ └──...