Change Request: Add docker support
See original GitHub issueESLint version
all
What problem do you want to solve?
ESLint currently does not have official docker support. While it is certainly possible to build a custom container, for CI pipelines that introduces unnecessary overhead. Also it makes it impossible to do a ‘quick-one-off’. e.g. while it is possible to do eslint file.js
on a local system, if a user does not want the overhead of installing all the dependencies (npm etc) and would much prefer to use a docker container, they currently have to rely 3rd party containers.
CI systems fall into the same category, where building custom images or using 3rd party images are fine, they make it harder then it should be.
What do you think is the correct solution?
From usability AND security point of view, offering an official ESLint Docker container is by far the most ideal solution.
Participation
- I am willing to submit a pull request for this change.
Additional comments
While in terms of process, #15430 has been already closed, I believe it checks all the marks.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top GitHub Comments
As far as I’m aware, shellcheck, shfmt, and hadolint don’t have plugins. Is that correct? So many ESLint users include plugins, which removes the big benefit of having a pre-build Docker image. Users would still need to run an install step inside the container before running
eslint
. They’d have to either maintain a separate dependency manifest just for ESLint and its plugins or accept redundantly installing CI-related dependencies twice - once in the ESLint container and once to run other CI tasks.Yeah, sure, no problem. Sad that you don’t want to support all your users (especially from a security PoV) and just prefer people roll their own 😦
Such is life!