A build for the browser

[mercmobily]

I need to run Eslint in the browser. I am going totally insane trying to do it.
I realise you don't want to support the browser environment. However, I can't work out how to create a browser-consumable bundle with all of the rules baked in, which I can then load from the browser (specifically, for CodeMirror 6).

This repository https://github.com/satya164/eslint-browser is some 2400 commits behind (last commit, 5 years ago). I am thinking I could try browserify.

Before I start with more head banging, can I ask... How do you guys make the bundle for the demo exactly?

And... are you sure it's not worthwhile to at least provide some guidance for this?

[nzakas]

We don’t want to support a browser build because it will require a lot more maintenance on our part. ESLint was never intended to run in the browser but we are kind of hacking it. We can’t guarantee that the way we do it now will continue to work in the long run.

But in general, you should be able to Webpack the Linter class and have it work in a browser:

https://github.com/eslint/eslint/blob/main/webpack.config.js

[jsudelko]

Done right, supporting the browser should reduce maintenance. There are a lot of competing platforms: Node, Deno, Bun, Cloudflare and friends where people may conceivably want to run their code (and probably one or two more within the decade). These platforms are now converging towards supporting browser APIs and as such supporting the browser as a first class citizen improves portability and decreases maintenance.

Even for tools mostly used outside the browser, there's increasing consensus (particularly for newer JS tooling) that the way to go is to have the core runnable entirely in the browser, and adapters for other platforms such as Node, Deno etc. These could be supported by the ESLint team or the community as need arises.

[nzakas]

Already being discussed. See #16557.

[mercmobily]

Is that webpack config what you use at the moment for your demo?

…

On Wed, 30 Mar 2022 at 08:24, Nicholas C. Zakas ***@***.***> wrote: We don’t want to support a browser build because it will require a lot more maintenance on our part. ESLint was never intended to run in the browser but we are kind of hacking it. We can’t guarantee that the way we do it now will continue to work in the long run. But in general, you should be able to Webpack the Linter class and have it work in a browser: https://github.com/eslint/eslint/blob/main/webpack.config.js — Reply to this email directly, view it on GitHub <#15733 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQHWXWF4ZBV6QBNIEIECXDVCONNJANCNFSM5R3TX7OQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mercmobily]

(I am assuming it would ever make sense to load a plugin in a browser context... does it?)

[aladdin-add]

as it needs to know to load which plugins ("plugins" were configured in the eslintrc). So, with the linter, if you want to use rules in a 3rd-party plugin, you'll get an error like "Definition for rules 'xxx' was not found."

[mercmobily]

I understand. But aren't plugins loaded via a dynamic require()? Why fs in that case? (This is my last question regardless -- thank you)

[aladdin-add]

emm..maybe you are right. but it did need some node.js builtin-modules, so you cannot use it directly on browsers.
(I'm on a mobile, so cannot search where it was used 😄 )

[mercmobily]

No worries at all. Thank you!