search

eamodio / vscode-tsl-problem-matcher

TypeScript + Webpack Problem Matchers for VS Code
MIT License
44 stars 9 forks source link

Changed ID? #10

Closed joaomoreno closed 3 years ago

joaomoreno commented 3 years ago

The Marketplace tells me amodio.tsl-problem-matcher is the new ID for this extension. Is this correct?

alefragnani commented 3 years ago

It seems all extensions were updated, except GitLens (which now shows as GitKraken).

felipecrs commented 3 years ago

I forked this project and published a new version of it:

https://marketplace.visualstudio.com/items?itemName=felipecrs.tsl-problem-matcher

It contains proper support for webpack-cli@4, which requires additional configuration.

@joaomoreno https://github.com/microsoft/vscode-generator-code/pull/305

eamodio commented 3 years ago

@joaomoreno Yeah that is the new ID. I had to move my other extensions to not affect GitLens' ownership change. I've published a new 0.5.0 version with the new ID and Webpack 5 changes.

alefragnani commented 3 years ago

@eamodio I suppose the publisher difference may be the reason why Project Details section remains empty on your other extensions.

eamodio commented 3 years ago

@alefragnani Ah, apparently -- seems to get fixed when I publish an updated version with the new id.

felipecrs commented 3 years ago

@eamodio I made a PR to fine tune the documentation: https://github.com/eamodio/vscode-tsl-problem-matcher/pull/11.

I think you documented the steps for webpack-cli v3 where it was v4, and vice-versa.

On my tests, the version of webpack is not important, but only the webpack-cli. And there are some corner cases, such >= 4.0 < 4.3 not being supported.

felipecrs commented 3 years ago

Also, I will be deprecating my fork in favor of this one again. Thank you.