-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add webpack dummy build as a lint step #2626
Conversation
webview/package.json
Outdated
@@ -7,6 +7,7 @@ | |||
"lint:prettier": "prettier -c '**/*.{js,json,jsx,md,scss,ts,tsx,yaml,yml}'", | |||
"lint:eslint": "eslint --cache '**/*.{js,ts,jsx,tsx}'", | |||
"lint:tsc": "tsc --noEmit", | |||
"lint:webpack": "webpack --mode development", |
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.
[Q] Do we need lint:tsc
if we have this? Could we change to lint:compile
for all sub-projects? Leave extension
as is but change the two sub-projects bundled by webpack to use this?
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.
That's a good point, thanks! I'll add lint:compile to the two webpacked projects and remove lint:tsc from them
56b43c3
to
f515691
Compare
Code Climate has analyzed commit f515691 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (85% is the threshold). This pull request will bring the total coverage in the repository to 96.8% (0.0% change). View more on Code Climate. |
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.
Looks good to me!
This PR will add webpack --mode development as a linting step.
The objective is to catch bundling errors that tsc --no-emit ignores, like styles.scss imports, for example.