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

chore: yarn_pnp tests uses gatsby-dev-cli instead of portals #35699

Merged
merged 11 commits into from May 20, 2022

Conversation

LekoArts
Copy link
Contributor

@LekoArts LekoArts commented May 19, 2022

Description

yarnpkg/berry#4443 won't be resolved soon. So we'll need to update our yarn pnp tests to not use portals anymore. With some modifications we can use gatsby-dev-cli.

Related Issues

[ch50764]

Unblocks #35446

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 19, 2022
@LekoArts LekoArts added topic: automation Related to Circle CI, Peril, Renovate, scripts/*, Github Workflows, Github Actions, or Slackbot and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels May 19, 2022
@LekoArts LekoArts marked this pull request as ready for review May 20, 2022 08:53
@LekoArts LekoArts changed the title chore: yarn_pnp tests use gatsby-dev-cli chore: yarn_pnp tests uses gatsby-dev-cli instead of portals May 20, 2022

#### `--external-registry`

Run `yarn add` commands without the `--registry` flag. This is helpful when using yarn 2/3 and you need to use `yarn config set npmRegistryServer http://localhost:4873` for `gatsby-dev-cli` to work.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Run `yarn add` commands without the `--registry` flag. This is helpful when using yarn 2/3 and you need to use `yarn config set npmRegistryServer http://localhost:4873` for `gatsby-dev-cli` to work.
Run `yarn add` commands without the `--registry` flag. This is helpful when using yarn 2/3 and you need to use `yarn config set npmRegistryServer http://localhost:4873` and `echo -e 'unsafeHttpWhitelist:\n - "localhost"' >> .yarnrc.yml` before running `gatsby-dev-cli`.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can be skipped from that PR for the sake of landing this faster

Copy link
Contributor

@pieh pieh left a comment

Choose a reason for hiding this comment

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

This can go in as-is, I just left one suggestion so README list all needed "commands" for yarn 2/3 to work

@LekoArts LekoArts merged commit 972e6e1 into master May 20, 2022
@LekoArts LekoArts deleted the yarn-3-dev-cli branch May 20, 2022 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: automation Related to Circle CI, Peril, Renovate, scripts/*, Github Workflows, Github Actions, or Slackbot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants