Eric Amodio

Thanks -- fyi, it seems somewhat like a bug right now that a jsonpath query like `{{data.response.body.$.json.teams[*].id}}` is currently equivalent to `{{data.response.body.$.json.teams[0].id}}`

@talcodota While I can certainly understand that -- I would just recommend looking into this sooner than later. Given more and more users are using VS Code with containers, remote...

This would be awesome. It would also be great to be able to "cycle" through the defined tags when toggling a bookmark (optional of course - or a separate command)....

FYI I opened this vscode issue: https://github.com/Microsoft/vscode/issues/33852

While I agree that webpack should fix the start/end watch mode issue, https://github.com/webpack/webpack/issues/5895 is closed. Hopefully it can be reconsidered. But it would be great if the error output matched...

I've gotten things working decently well with this problem matcher for both `ts-loader` and `tslint-loader`: ```json "problemMatcher": [ { "fileLocation": "absolute", "owner": "typescript", "pattern": [ { "regexp": "\\[tsl\\] ERROR in...

If you aren't using multiple configs (i.e. returning an array from your webpack config) (See: https://github.com/webpack/webpack/issues/7906), it looks like you can use `webpack --watch --info-verbosity verbose` to get lifecycle start...

Sorry no docs PR yet, but I published [TypeScript + Webpack Problem Matchers](https://marketplace.visualstudio.com/items?itemName=eamodio.tsl-problem-matcher) for vscode that provides a set of problem matchers for `ts-loader` and `tslint-loader`

@ClementVidal Yeah, I was wrong that it would be enough to be very accurate -- although it gets a lot closer than any other options right now. I still do...

AFAIK, problems will never clear until there is a new compile when using the problem matchers, since there is no trigger to update them.