Created by: wileybenet
When specifying a --scripts-version, the first @ in a scoped package prevents the packageName from being trimmed of its version tag, if it has one. Hence, an uncaught error is thrown when the full, pinned package name is used in the path to read package.json:
I added the .match() to yield a truthy value if the installPackage contains an @ symbol at char 0 and at char 1+. To test that this works, run create-react-app --scripts-version=@organization/my-react-scripts@0.0.1 and see that create-react-app completed successfully and that the correct package version was installed:
