Michaël De Boey

I've been thinking this a couple of times already, so since we're discussing examples organisation here: I think it could also help if we would rename https://github.com/remix-run/examples to `remix-examples` and...

Original answer by @AriPerkkio in https://github.com/testing-library/eslint-plugin-jest-dom/pull/372#pullrequestreview-2357178113 > This version requires `eslint@9` and `eslint-remote-tester@4`: > > - https://github.com/AriPerkkio/eslint-remote-tester-run-action/releases/tag/v5 > - https://github.com/AriPerkkio/eslint-remote-tester/releases/tag/v4.0.0 > > `eslint-remote-tester@4` requires configuration file to be flat config.

@ddrozdov This plugin (currently) doesn't support `@testing-library/react-native`. I'll let @Belco90 decide what to do with this, but imo we should not add this and add full support in 1 go...

@ddrozdov I just think we should make sure we take time to check if all rules are supporting RN before say we officially support RN in this plugin For the...

@brophdawg11 Forgot to rename the file to remove in `remix.init` 🙈 Should be fine now

@brophdawg11 I've added the `--esm` flag to the seed script 👍 I also updated `module` in `tsconfig.json` to `ES2020` as `ts-node` wasn't recognizing `import` statements when `module` is set to...

@pcattori I've updated this stack to use `NODE_OPTIONS` instead, but I still get the ESM error @brophdawg11 mentioned when running `npm run dev`/`npm run dev:serve`/`npm run start:mocks`

@mcansh `--import` was only introduced in Node v19 though and the stack currently supports v14 As we're almost releasing Remix v2, we could go for v18 already I think, but...

@brophdawg11 I just ran the command you posted and the seed works fine on my end `dev:serve` is still failing without @mcansh's https://github.com/remix-run/remix/pull/7348 though

@brophdawg11 I'm on Node v16