-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added TypeScript to make code base easier to maintain #35
Conversation
|
||
/* Strict Type-Checking Options */ | ||
"strict": true, /* Enable all strict type-checking options. */ | ||
"noImplicitAny": true, /* Raise error on expressions and declarations with an implied 'any' type. */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears we don't have implicit any
's anywhere, so I think it'd be better to turn this flag off.
Edit: oops, the flag is on; it's just that it's not necessary since it's implied by strict: true
:)
"noImplicitAny": true, /* Raise error on expressions and declarations with an implied 'any' type. */ | |
// "noImplicitAny": true, /* Raise error on expressions and declarations with an implied 'any' type. */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a lot of added optional
keys added in package-lock.json
, which is due to your using the npm from Node 12 instead of the one from Node 10 that was used previously. Could you either regenerate it with Node 10, or add an .nvmrc
with 12
as its contents, indicating that everybody should be using that?
Also adding .nvmrc so it's easier to be consistent about being on the same version
@Vinnl I've added a .nvmrc file and regenerated package-lock.json with Node v8.16.0. |
Adding prettier and Standard JS to maintain code base better
No description provided.