Jim Cresswell
Jim Cresswell
I have just spent this afternoon on exactly this issue, running the action in a Github workflow triggered by a `pull_request` event and seeing no check status from the upload...
I'm running into the same issue with `deployment_status` events.
@Fedeorlandau I have a very similar issue. I need to run various checks after a @Vercel `deployment_status` event, but their event sets the `ref` field to have the value of...
> FWIW, the recommendation is to use https://nextjs.org/docs/basic-features/environment-variables which has safety checks to exclude environment variables that are only meant for the server. @balazsorban44 absolutely, I just wanted to clarify...
This would be useful for us too. Happy to help if that's possible.
Hi @nicojs, okay that's really interesting, I hadn't realised Babel was fundamental to Stryker. I've attached the [console output](https://github.com/stryker-mutator/stryker-js/files/8510939/stryker.log) from invoking StrykerJS with `npm run stryker run`, and the config...
Ahh, both of those commands succeed! Our Jest config uses the [Next.js Jest config](https://nextjs.org/docs/testing#setting-up-jest-with-the-rust-compiler), like ```javascript // jest.config.js const nextJest = require("next/jest"); const createJestConfig = nextJest({ // Provide the path...
Okay! I've run that with updated config ```javascript const path = require("path"); /** * @type {import('@stryker-mutator/api/core').StrykerOptions} */ module.exports = { _comment: "This config was generated using 'stryker init'. Please take...
Good news! Feels like it should work. It's an async function, like this [example in the Jest docs](https://jestjs.io/docs/configuration) ```javascript // Or async function module.exports = async () => { return...