Closed glensc closed 1 year ago
i'm not sure i follow your question. the purpose of this plugin is to easily integrate eslint into your development workflow. this allows you to easily check for code style errors, etc., while you work on things. eslint will then pretty-print a summary of errors and warnings into your console.
this plugin however is not to bundle eslint into a chunk. which is what you were trying to do, if i understand your snippet correctly, right?
yes, I want to bundle. but why this plugin is needed? why can't I just use eslint itself?
you absolutely can use eslint on its own, you don't have to use this plugin. the plugin is only to make linting your source code easier, to automatically make eslint run when esbuild starts a (re)build. but if you want to somehow integrate eslint into a bundle, this plugin won't help you with that.
i still don't understand why this plugin is useful, why would i want to use this plugin (instead of eslint directly). can you make https://asciinema.org/ recording to show it's usefulness?
i personally run eslint with lint-staged, so it's executed on every commit.
I'm looking for a way to create eslint bundle, i.e one file eslint.js with all necessary dependencies from node_modules bundled in to that file. because of dynamic imports, out of the box it does not work:
I setup your plugin into
build()
pipeline, and it still gave me formatters/stylish import error.Similarly for bundling pino, there's plugin that handles the dynamic imports for bundling:
but this project, given the same project name structure, and usage, does something different. what does it mean? because these two sentences definitely doesn't explain it. to me:
please describe the actual usage of this plugin in readme, perhaps with examples, asciicast?