Why are you complaining about npm compatibility while also complaining that they don’t have enough compatibility? Sounds like you want it both ways — for it to be very simple and purposeful, but also to broadly support lots of options from the Node ecosystem.
Their purpose is to be a single toolchain & system for JS, and they’re solving a lot of problems in that area. No need to configure huge number of tools for a reasonable professional, production setup — even built in Otel! And if that’s their goal, why would they spend time on complete eslint compatibility? That’s the old world.
I will re-frame it for you with emphasis. I do not want the complexity of npm compatibility in Deno. However, if they insist on it, then I at least want to be able to use my existing linting setup for consistency. That is the one silver lining that I would want to make use of. Yet, I can’t.
Instead, I got all the complexity without the benefit. That’s how I feel about it.
Their purpose is to be a single toolchain & system for JS, and they’re solving a lot of problems in that area. No need to configure huge number of tools for a reasonable professional, production setup — even built in Otel! And if that’s their goal, why would they spend time on complete eslint compatibility? That’s the old world.