Style guidelines

[ChildishGiant]

Currently the project has a basic .eslintrc set up but I think it'd make contributing easier and more consistent if we opted to use js standard style. Many projects (including npm, GitHub and the UK government) use this style

[wuda-io]

From my point of view this is ok. What are the risks? Is it possible that some parts are not working then or is it just the style-formating of the code?

[ChildishGiant]

Most of the rules can be automatically fixed (and there's a very simple option to autofix everything). Some things cannot and would be highlight and need manually fixing (not too difficult)

[ChildishGiant]

If we did our best to use conventional commit style that'd be a great help to future releases as changelogs could then be automatically generated. There are many tools for enforcing/suggesting this and also for making writing these commits as easy as possible.

[DanielRuf]

If we did our best to use conventional commit style that'd be a great help to future releases as changelogs could then be automatically generated. There are many tools for enforcing/suggesting this and also for making writing these commits as easy as possible.

Should we apply commitlint using https://www.npmjs.com/package/husky?

[ChildishGiant]

The issue is about code style, not just commit style, I don't think it can be closed yet.

[wuda-io]

Can we close it now? The conventional commit style is now enforced via Husky. Please confirm and/or close.

[LoganTann]

Can we close it now? The conventional commit style is now enforced via Husky. Please confirm and/or close.

As said in the comment above, this original issue is about enforcing the code style (indentation, etc.), not only the commit message format.