Open
Description
openedon Jun 26, 2018
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When using the --registry option on yarn create, the create-... package is being incorrectly loaded from https://registry.yarnpkg.com instead of the registry given in the option.
If the current behavior is a bug, please provide the steps to reproduce.
Given that usage info says:
$ yarn help create
warning package.json: No license field
Usage: yarn [command] [flags]
Creates new projects from any create-* starter kits.
Options:
...
--registry <url> override configuration registry
Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.
I have tried the following without success:
$ yarn --registry https://example.com/artifactory/ create @org/app
$ yarn --registry="https://example.com/artifactory/" create @org/app
$ yarn create --registry="https://example.com/artifactory/" @org/app
$ yarn create @org/app --registry="https://example.com/artifactory/"`
All produce the same error:
error An unexpected error occurred: "https://registry.yarnpkg.com/@org%2fcreate-app: Not Found".
What is the expected behavior?
@org/create-app would be installed from https://example.com/artifactory/ instead of https://registry.yarnpkg.com/.
Please mention your node.js, yarn and operating system version.
$ node --version
v8.11.3
$ yarn --version
1.7.0
$ uname -v
Darwin Kernel Version 17.6.0: Tue May 8 15:22:16 PDT 2018; root:xnu-4570.61.1~1/RELEASE_X86_64
macOS High Sierra 10.13.5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
