Add code linting (eslint) as part of CI script

[smoya]

Reason/Context

The number of JS files is growing lately, and I feel it's about time to let all these code pass through a code linter in order to ensure consistency and follow standards, also to find and fix potential bugs.

Description

• Install eslint package as dev dependency
• Create .eslintrc and .eslintrcignore files based on, for example, parser-js. Be aware this project doesn't use TypeScript, so modification of those files might be needed.
• Add new scripts. npm lint and npm lint:fix as, for example, parser-js has.
• Ensure the linter runs on CI (GitHub actions) on each PR.

[AnimeshKumar923]

I would like to work on this issue.

[smoya]

I would like to work in this issue.

Of course! Feel free to create a PR at anytime 🚀

[Gmin2]

@AnimeshKumar923 can i go ahead with this

[AnimeshKumar923]

@smoya I would like to give @Min2who this issue.

@Min2who Please go ahead with this issue 👍

[Gmin2]

@smoya I would like to give @Min2who this issue.

@Min2who Please go ahead with this issue 👍

thnx @AnimeshKumar923

[AnimeshKumar923]

thnx @AnimeshKumar923

Welcome! Let me know if you encounter any difficulties...

[Gmin2]

@smoya @AnimeshKumar923 how do i ensure this

[AnimeshKumar923]

@smoya @AnimeshKumar923 how do i ensure this

About this, @smoya If I rememeber correctly, Lukasz talked about modifying the workflows in .github repositories. So should we open a PR modifying the CI in if-nodejs-pr-testing.yml file to include the linting?

Because if we modify in this repo, it will later be overwritten. So to make it permanent, we should follow the above said approach. Thoughts? 👀

---

context: #452 (review)

[smoya]

@smoya @AnimeshKumar923 how do i ensure this

About this, @smoya If I rememeber correctly, Lukasz talked about modifying the workflows in .github repositories. So should we open a PR modifying the CI in if-nodejs-pr-testing.yml file to include the linting?

Because if we modify in this repo, it will later be overwritten. So to make it permanent, we should follow the above said approach. Thoughts? 👀

---

context: #452 (review)

The workflow is already calling the lint script https://github.com/asyncapi/.github/blob/master/.github%2Fworkflows%2Fif-nodejs-pr-testing.yml#L74-L75

[AnimeshKumar923]

The workflow is already calling the lint script https://github.com/asyncapi/.github/blob/master/.github%2Fworkflows%2Fif-nodejs-pr-testing.yml#L74-L75

Okay, then as I can see in #473, it will be executed after merging.
cc: @Min2who

[Gmin2]

thnx @smoya @AnimeshKumar923 for the info

[asyncapi-bot]

🎉 This issue has been resolved in version 6.4.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀