You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Manually adding a wildcard to the blueprint path from react-project's end of things doesn't work as a fix, as cp() will try to fs.statSync() it, which blows up with ENOENT on Windows.
I've got it working by manually tweaking the path separator cp() is checking for in react-project's node_modules/, but tweaking cp() to handle platform-normalised input paths properly would be a bigger, less fun job.
I've found copy-template-dir useful for this task cross-platform before - it also handles stripping a leading '_' from file names when copying, so blueprint dotfiles and package.json won't get picked up at unwanted times (e.g. npm will find and usefiles config in package.json at any level in your project when publishing). This could also be a potential fix for #8
The text was updated successfully, but these errors were encountered:
shelljs'
cp()
is checking for a source path ending with'/'
before adding a wildcard to it, but as the blueprint directory is built withpath.join()
, it will be in Windows'\'
format by the time shelljs gets it.Manually adding a wildcard to the blueprint path from react-project's end of things doesn't work as a fix, as
cp()
will try tofs.statSync()
it, which blows up with ENOENT on Windows.I've got it working by manually tweaking the path separator
cp()
is checking for in react-project'snode_modules/
, but tweakingcp()
to handle platform-normalised input paths properly would be a bigger, less fun job.I've found copy-template-dir useful for this task cross-platform before - it also handles stripping a leading
'_'
from file names when copying, so blueprint dotfiles andpackage.json
won't get picked up at unwanted times (e.g. npm will find and usefiles
config inpackage.json
at any level in your project when publishing). This could also be a potential fix for #8The text was updated successfully, but these errors were encountered: