Support templates in scoped packages#7991
Conversation
|
Hi klasbj! Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file.In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
|
Thanks @klasbj, this looks great. |
|
Thanks again! |
Fixing issue #7985.
I learned a bit about some... interesting... NPM behavior while testing. With only a regex check that the package name started with
cra-template-, it still fell back tocra-template-@scope/package. Ifscope/packagehappened to be an accessible Github project, npm would download and install some version (I'm not quite sure how it decided which version...) of that repository as the template.The solution I came up with was adding the prefix to the package name, while leaving the scope part unchanged. Maybe not 100% intuitive, but consistent with the behaviour of non-scoped packages.
Test cases
Plain, uses
cra-templateTemplate without prefix (
typescript), usescra-template-typescriptTemplate with prefix (
cra-template-typescript)Template in scoped npm package with prefix (
@klasbj/cra-template-scoped)Template in scoped npm package without prefix (
@klasbj/scoped), uses@klasbj/cra-template-scopedScoped template with matching Github project, attempts to use
@klasbj/cra-template-scoped-cra-template, and not my Github projectklasbj/scoped-cra-template