Skip to content
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

Inform users that choose webpack to install problem matcher extension #303

Closed
miguelsolorio opened this issue Sep 28, 2021 · 7 comments
Closed
Assignees
Milestone

Comments

@miguelsolorio
Copy link

Originally from #298

I created a brand new extension using the yo code command and when running it (with no modifications) I notice that I get a The Task 'npm: watch' cannot be tracked. Make sure to have a problem matcher defined. error and am not sure if this is a task issue or a generator problem.

CleanShot.2021-09-28.at.10.10.34.mp4

Version: 1.61.0-insider (Universal)
Commit: 214ac689ca9874a8a4be386f73d5cb60e15af25e
Date: 2021-09-28T05:14:06.244Z
Electron: 13.4.0
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 20.6.0

@alexr00
Copy link
Member

alexr00 commented Sep 29, 2021

@misolori did you choose to webpack your extension when going through the generator?

@miguelsolorio
Copy link
Author

@alexr00 yes I did, anything else I can do?

@alexr00
Copy link
Member

alexr00 commented Sep 30, 2021

Looks like the default build task when you choose the webpack options requires that you install the Typescript + Webpack Problem Matchers (eamodio.tsl-problem-matcher) extension. Do you have that installed?

@miguelsolorio
Copy link
Author

I don't have that installed, installing it makes the problems go away. Maybe this should be mentioned in the generator or somewhere else as I don't think people would be able to figure that out on their own?

@miguelsolorio miguelsolorio reopened this Oct 11, 2021
@miguelsolorio miguelsolorio transferred this issue from microsoft/vscode Oct 11, 2021
@miguelsolorio miguelsolorio changed the title Running a new extension fails to run on first attempt Inform users that choose webpack to install problem matcher extension Oct 11, 2021
@miguelsolorio
Copy link
Author

Updated the title to reflect the issue

@aeschli
Copy link
Contributor

aeschli commented Oct 23, 2021

I added a message to the generator.

@aeschli aeschli assigned aeschli and unassigned alexr00 Oct 23, 2021
@aeschli aeschli added this to the October 2021 milestone Oct 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@aeschli @miguelsolorio @alexr00 and others