crfrolik

> As long as any are still in View Engine format, then you still require ngcc, which will mutate node_modules. In that case, would it be possible to get a...

It seems that it is not maintained anymore. You might want to avoid using it for now.

It's worth noting that the [Angular roadmap](https://angular.io/guide/roadmap#angular-devtools) has an upcoming feature for a new "Angular devtools" which looks like a replacement for Augury. I don't know when that is coming,...

Is this project going to be updated for Ivy? I haven't seen any progress in the commit history recently.

I'd like to point out that the `original-fs` package has an LGPL license, which may be undesirable for some users. If you're using webpack, it should be safe to use...

Well, I figured out that I can fix it with `syncpack format`, but I think some indication of what's going on would still be helpful.

It would be nice to have granular output about the specific problems, yes. Also, maybe the tool could direct me to `syncpack format` as a way to fix those problems?...

Is there an update on the progress of this? Using papaparse in a project with `"type":"module"` (via `tsx`) gives me this error: ``` import { parse, ParseResult } from 'papaparse';...

The warning message is misleading. At first glance, it's tempting to think that it might be coming from your repo/project. If you're like me, you might run `npx update-browserslist-db@latest` thinking...

Just encountered this. Is there a workaround? ``` Oops! Something went wrong! :( ESLint: 9.1.1 TypeError: context.getAncestors is not a function Occurred while linting [...]/test/common-helpers.ts:240 Rule: "chai-friendly/no-unused-expressions" at ExpressionStatement ([...]/test/node_modules/eslint-plugin-chai-friendly/lib/rules/no-unused-expressions.js:262:50)...