Is there a 0.1% chance that we could solve the plain js vs modules problem without a special extension and without perf penalties?
It's well understood to mean "some kind of JS, look elsewhere for the precise meaning"
-
-
Exactly, it is imprecise so not well understood
-
It means "JavaScript content". That's most important for tools like syntax highlighters or simple code search tools.
-
These tools exist in many many places. We can fix popular ones but there's a long tail.
-
Agree, but those tools arent evaluating code. We can PR safely over time.
-
We can but the long tail cost will be annoying. Some tools might be unmaintained and embedded in enterprise apps
-
Will they start adding new parsers? Will they handle ESM at all? If that doesnt update why would app?
-
Syntax highlighters don't parse, they lex. They're very simple and don't care about stuff like auto-strict
-
Some, but others like https://gist.github.com/bmeck/05f5ac4ae58b052782927ba70dc4caf6parse … it.
End of conversation
New conversation -
-
-
There's no reason why modules suddenly change that strategy.
-
Modules change it so hosts need to support multiple eval modes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.