Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests(remix-dev): update to React v18 #3929

Merged
merged 1 commit into from
Aug 8, 2022

Conversation

MichaelDeBoey
Copy link
Member

This shouldn't have been done in #3917, as package.json is updated to React v18

@changeset-bot
Copy link

changeset-bot bot commented Aug 5, 2022

⚠️ No Changeset found

Latest commit: 2370829

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Member

@kentcdodds kentcdodds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Solid 👍

@kentcdodds kentcdodds merged commit 0310826 into remix-run:dev Aug 8, 2022
@MichaelDeBoey MichaelDeBoey deleted the update-tests-to-react-18 branch August 8, 2022 22:46
@MichaelDeBoey MichaelDeBoey added the awaiting release This issue has been fixed and will be released soon label Aug 9, 2022
mcansh pushed a commit that referenced this pull request Aug 11, 2022
@MichaelDeBoey MichaelDeBoey removed the awaiting release This issue has been fixed and will be released soon label Aug 12, 2022
pcattori added a commit that referenced this pull request Nov 14, 2022
this fixture was incorrectly included as part of dependency upgrades:
- #3917
- #3929

it should not have been updated since it is supposed to represent a
Remix 1.3.x codebase
pcattori added a commit that referenced this pull request Nov 14, 2022
this fixture was incorrectly included as part of dependency upgrades:
- #3917
- #3929

it should not have been updated since it is supposed to represent a
Remix 1.3.x codebase
pcattori added a commit that referenced this pull request Nov 14, 2022
this fixture was incorrectly included as part of dependency upgrades:
- #3917
- #3929

it should not have been updated since it is supposed to represent a
Remix 1.3.x codebase
pcattori added a commit that referenced this pull request Nov 15, 2022
this fixture was incorrectly included as part of dependency upgrades:
- #3917
- #3929

it should not have been updated since it is supposed to represent a
Remix 1.3.x codebase
pcattori added a commit that referenced this pull request Nov 15, 2022
this fixture was incorrectly included as part of dependency upgrades:
- #3917
- #3929

it should not have been updated since it is supposed to represent a
Remix 1.3.x codebase
pcattori added a commit that referenced this pull request Nov 15, 2022
…`-based codemods (#4572)

* refactor(dev): extract `useColor` usages into `safe` utility

* refactor(dev): remove outdated reference to compiler shims

* fix(dev): remove access to `convert-to-javascript` migration via CLI

conversion to javascript is not a "migration" in that it does not help the user to upgrade to a
newer version of Remix

* refactor(dev): rewrite `replace-remix-magic-exports` as a babel codemod

Compared to the previous jscodeshift-based migration:
- codemod no longer depends on a network connection
- babel's visitor API for traversing the AST is simpler
- not spinning up workers for applying code transforms

This ends up speeding up the codemod by ~10x and (hopefully 🤞) fixes
some of the issues we were seeing in CI on Windows (since we think
problems are mostly timeouts caused by slow tests or overhead for
workers).

* test(dev): restore fixture

this fixture was incorrectly included as part of dependency upgrades:
- #3917
- #3929

it should not have been updated since it is supposed to represent a
Remix 1.3.x codebase

* test(dev): add tests for generic codemods and specifically for `replace-remix-magic-imports`

* ci: run build before primary tests

some tests can make use of the built javascript artifacts
(e.g. `cli.js`) to run 8-10x faster than running with source
Typescript (e.g. `cli.ts`)

* test(dev): retry temp dir removal for windows ci

Windows sometimes throws `EBUSY: resource busy or locked, rmdir`
errors when attempting to removing the temporary directory.
Retrying a couple times seems to get it to succeed.
See https://github.com/jprichardson/node-fs-extra/issues?q=EBUSY%3A+resource+busy+or+locked%2C+rmdir

* Create long-colts-remain.md
kentcdodds pushed a commit that referenced this pull request Dec 15, 2022
…`-based codemods (#4572)

* refactor(dev): extract `useColor` usages into `safe` utility

* refactor(dev): remove outdated reference to compiler shims

* fix(dev): remove access to `convert-to-javascript` migration via CLI

conversion to javascript is not a "migration" in that it does not help the user to upgrade to a
newer version of Remix

* refactor(dev): rewrite `replace-remix-magic-exports` as a babel codemod

Compared to the previous jscodeshift-based migration:
- codemod no longer depends on a network connection
- babel's visitor API for traversing the AST is simpler
- not spinning up workers for applying code transforms

This ends up speeding up the codemod by ~10x and (hopefully 🤞) fixes
some of the issues we were seeing in CI on Windows (since we think
problems are mostly timeouts caused by slow tests or overhead for
workers).

* test(dev): restore fixture

this fixture was incorrectly included as part of dependency upgrades:
- #3917
- #3929

it should not have been updated since it is supposed to represent a
Remix 1.3.x codebase

* test(dev): add tests for generic codemods and specifically for `replace-remix-magic-imports`

* ci: run build before primary tests

some tests can make use of the built javascript artifacts
(e.g. `cli.js`) to run 8-10x faster than running with source
Typescript (e.g. `cli.ts`)

* test(dev): retry temp dir removal for windows ci

Windows sometimes throws `EBUSY: resource busy or locked, rmdir`
errors when attempting to removing the temporary directory.
Retrying a couple times seems to get it to succeed.
See https://github.com/jprichardson/node-fs-extra/issues?q=EBUSY%3A+resource+busy+or+locked%2C+rmdir

* Create long-colts-remain.md
brophdawg11 pushed a commit to remix-run/react-router that referenced this pull request Mar 27, 2024
…`-based codemods (#4572)

* refactor(dev): extract `useColor` usages into `safe` utility

* refactor(dev): remove outdated reference to compiler shims

* fix(dev): remove access to `convert-to-javascript` migration via CLI

conversion to javascript is not a "migration" in that it does not help the user to upgrade to a
newer version of Remix

* refactor(dev): rewrite `replace-remix-magic-exports` as a babel codemod

Compared to the previous jscodeshift-based migration:
- codemod no longer depends on a network connection
- babel's visitor API for traversing the AST is simpler
- not spinning up workers for applying code transforms

This ends up speeding up the codemod by ~10x and (hopefully 🤞) fixes
some of the issues we were seeing in CI on Windows (since we think
problems are mostly timeouts caused by slow tests or overhead for
workers).

* test(dev): restore fixture

this fixture was incorrectly included as part of dependency upgrades:
- remix-run/remix#3917
- remix-run/remix#3929

it should not have been updated since it is supposed to represent a
Remix 1.3.x codebase

* test(dev): add tests for generic codemods and specifically for `replace-remix-magic-imports`

* ci: run build before primary tests

some tests can make use of the built javascript artifacts
(e.g. `cli.js`) to run 8-10x faster than running with source
Typescript (e.g. `cli.ts`)

* test(dev): retry temp dir removal for windows ci

Windows sometimes throws `EBUSY: resource busy or locked, rmdir`
errors when attempting to removing the temporary directory.
Retrying a couple times seems to get it to succeed.
See https://github.com/jprichardson/node-fs-extra/issues?q=EBUSY%3A+resource+busy+or+locked%2C+rmdir

* Create long-colts-remain.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants