Simen Bekkhus
Simen Bekkhus
Jest doesn't support `require.cache` anyways (we have explicit cache clearing APIs), so if I can treat `import(cjs)` and `require(cjs)` the same it actually simplifies the implementation. I think this should...
Yes please, that would be awesome 👍
Yup yup! Really straight forward to use 🙂
Yes please! I'm playing around with using the built in problem matchers for tsc and eslint, and it works swimmingly: https://github.com/facebook/jest/pull/9223. Would be awesome to just stick an action in...
The default jest output is certainly not suited. It should be a separate reporter (an idea might be that GitHub parses junit output?). Could probably reach out to GitHub about...
There shouldn't be an issue to create a reporter that outputs something a problem matcher can parse. I think that's a good idea, as we could ship it by default...
@stefanbuck sorry, missed your last message. I still think a dedicated reporter makes more sense than a problem matcher. However, we could probably output some json on a single line...
#134 and #143 are the main breaking things I was waiting on, very happy to see them land 😀 Beyond that I don't really know what's missing (@rclmenezes's list looks...
Probably just missing https://github.com/fastify/session/pull/154?
`includeRequires` was indeed what was needed. `{ test: /\.hbs$/, loader: 'handlebars', query: { inlineRequires: '\/images\/' } }` Could that option maybe get a more prominent spot in the docs? And...