Acorn VS Pylint

Why do we then have other JavaScript parsers like babel parser, swc parser, acorn, espree and the likes since JavaScript engines have their own internal parsers?

If you're trying to determine if a string is valid Javascript then your best bet is to use a JS parser like Acorn. Trying to DIY parsing with just regex is a good way to end up incredibly frustrated.

To render UI I use Svelte. To parse JS files I use Acorn JS in Web Worker.

Behind Babel is created by an Australian developer Sebastian McKenzie and now consists a small team of contributors. Babel also makes uses a polyfill library called core-js, which in turn uses a JavaScript parser, acorn.

At line 3, we import parseScript from meriyah which is a JavaScript parser (could have been babel, acorn, swc, etc doesn't matter for our use case as long as they correctly implement the spec).

A simple starting point is Acorn with estree-walker. Not sure if you'll need more advanced functionality but that pair has worked well for my usage. It's also the combo that Svelte uses internally.

https://github.com/acornjs/acorn For parsing the tree

A little introduction about pylint. Pylint is a static code analyzer, it analyses your code without actually running it. Pylint looks for potential errors, gives suggestions on coding standards that your code is not adhering to, potential places where refactoring might help, and also warnings about smelly code.

Pylint, on the other hand, focuses on code analysis and style checking. It offers extensive customization options and supports various coding standards. Pylint is known for its comprehensive reports and ability to detect a wide range of code issues.

In my opinion, the best way to expose configuration options is to read and parse them from the project's pyproject.toml file. Here's how Pylint handles it.

I even contributed to Pylint by submitting a new rule a few years ago : implicit-str-concat.

Implemented code formatting with Black and linting with Pylint in my CI pipeline. Here is my updated GitHub Actions Workflow file: ci.yml

One last thing to do before running the hooks is to create a config file, just like we did with flake8. For this you are going to create a pylintrc file at the roor of your project and copy the contents of the pylintrc file from the pylint repo (here is the link to it).