e.g.
```
"scripts": {
"doc": "jsdoc -c ./doc...
# sdfe
erictgrubaugh
05/15/2019, 6:28 PMe.g.
Copy code
"scripts": {
"doc": "jsdoc -c ./doc/conf.json",
"test": "mocha --opts .mocharc",
"posttest": "eslint --fix --config .eslintrc --ignore-path .eslintignore ./FileCabinet/SuiteScripts",
"postversion": "git push && git push --tags"
},c
chris
05/15/2019, 6:43 PMjust as good. i would love to
eslint --fixchris
05/15/2019, 6:43 PMalso, you can stuff all your estlintrc info into package.json btw
chris
05/15/2019, 6:43 PM Copy code
"eslintConfig": {
"env": {
"browser": true,
"commonjs": true
}, ...e
erictgrubaugh
05/15/2019, 6:59 PMRight; I definitely prefer configs for the various programs to be separate
erictgrubaugh
05/15/2019, 6:59 PMotherwise
package.jsonerictgrubaugh
05/15/2019, 7:00 PMbut I don't begrudge anyone else for using package.json 🙂
s
stalbert
05/15/2019, 8:51 PMdo you find eslint to provide useful value above and beyond tsc?
c
chris
05/15/2019, 9:17 PMyeah, i base it off of the airbnb config
chris
05/15/2019, 9:19 PMit allows multiple engineering teams to agree on the same code and style
chris
05/15/2019, 9:20 PMrather than each individual having a preference no one else has
e
erictgrubaugh
05/15/2019, 9:25 PMyes, and it's IDE-agnostic, which is even better for teams
👆 1
erictgrubaugh
05/15/2019, 9:25 PMfor a solo practitioner, probably not as useful, but I still use it
s
stalbert
05/16/2019, 2:03 PMah, I've just leaned on Webstorm's support for standardjs style along with an
.editorconfig