I have gotten used to working with a .editorconfig file to share settings across developers & editors, perhaps it will work for you? :)
the eslint config was generated by eslint based on the existing code style, adding plugins that seemed to make sense to me (for details on the latter, please see the package.json changes)
adds a test artifacts section to .gitignore (the MIDI file was generated as part of the build, which I assume should not be checked in. I did not include the accompanying fresh docs build in this PR though)
controller-change-event.jsControllerChangeEvent seems unused at present? but added missing import eslint spotted
writer.js one unused import eslint spotted
Apart from that, it's fixing mixed tab & spaces, trailing whitespace and "extra" semicolons eslint thought did not match the style of the rest of the codebase.
eslint now only moans about use of var and using a bitwise operator at the top of a loop, IIRC, but as these are more controversial I decided to leave them.
grimmdude
commented
5 years ago
.editorconfigfile to share settings across developers & editors, perhaps it will work for you? :)package.jsonchanges).gitignore(the MIDI file was generated as part of the build, which I assume should not be checked in. I did not include the accompanying fresh docs build in this PR though)package.json: alpha-sort npm scripts, adds eslint requirementscontroller-change-event.jsControllerChangeEventseems unused at present? but added missing import eslint spottedwriter.jsone unused import eslint spottedApart from that, it's fixing mixed tab & spaces, trailing whitespace and "extra" semicolons eslint thought did not match the style of the rest of the codebase.
eslint now only moans about use of
varand using a bitwise operator at the top of a loop, IIRC, but as these are more controversial I decided to leave them.