Skip to content

Conversation

@merceyz
Copy link
Member

@merceyz merceyz commented Apr 26, 2022

What's the problem this PR addresses?

Closes #4396

How did you fix it?

  • Update the error to indicate that the user is possibly attempting to import a built-in plugin.
  • Updated the range to match canary releases

Checklist

  • I have read the Contributing Guide.
  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

Comment on lines +26 to +35

test(
`it should detect attempts to import built-in plugins`,
makeTemporaryEnv({}, async ({path, run, source}) => {
await expect(run(`plugin`, `import`, `workspace-tools`)).rejects.toMatchObject({
code: 1,
stdout: expect.stringContaining(`is already installed`),
});
}),
);
Copy link
Member Author

Choose a reason for hiding this comment

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

This test will only work once this PR is merged due to the URL it fetches the range from

const REMOTE_REGISTRY = `https://raw.githubusercontent.com/yarnpkg/berry/master/plugins.yml`;

@arcanis arcanis merged commit e74ddff into master Apr 26, 2022
@arcanis arcanis deleted the merceyz/fix/plugin-import-builtin branch April 26, 2022 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Current canary fails when running yarn plugin import interactive-tools

3 participants