You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, cryptid-js has absolutely no linting or formatting rules: you can freely write code any way you want, commit it and push it. No restrictions, no checks. You can use tabs in one file and spaces in another (the horror! 😢).
Create the lint and lint:fix scripts in the package.json.
Obviously, lint:fix should run the linter with the --fix flag.
Configure eslint and prettier.
Please use separeate files, do not pollute the package.json with this configuration.
Please be aware, that cryptid-js is isomorphic: clients can use it on both the client-side and the server-side. The linting configuration should be aware of this scenario.
Brief
Currently, cryptid-js has absolutely no linting or formatting rules: you can freely write code any way you want, commit it and push it. No restrictions, no checks. You can use tabs in one file and spaces in another (the horror! 😢).
To improve upon this situation, we should set up a linting and formatting toolchain using eslint (https://eslint.org/) and prettier (https://prettier.io/).
Task
lint
andlint:fix
scripts in the package.json.lint:fix
should run the linter with the--fix
flag.Settings for Prettier
Please use the following settings for prettier:
The text was updated successfully, but these errors were encountered: