-
Notifications
You must be signed in to change notification settings - Fork 907
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
init
with local react-native fails with EISDIR
#186
Comments
cc @Esemesek who's working on new version of |
I am working on it. Right now, I don't think |
I avoided using Verdaccio on purpose, because publishing to a local npm after every edit is a bit of a pain and doesn't result in a pleasant edit-compile-debug cycle. |
I tried this briefly while moving codebase to separate repository and it seemed like it doesn't work. I agree that this is a painful flow to work with init. |
I think we should make sure it's still possible to init a project by setting path to a React Native version. In the future, given the new @fson, make sure to run Should be: $ react-native init HelloWorld --version /Users/ville/Projects/react-native/path-to-packed-files.tgz Since you are testing iOS only - there's no extra work you need to do. In order to be able to have Android sources up to date, you would have to build See releases script for the exact set of commands to run here and here |
Environment
Using fson/react-native@8048dc7 and
@react-native-community/cli@1.2.4
.Description
I was trying to test facebook/react-native#23563 end-to-end, so I ran
react-native init HelloWorld --version <path-to-local-react-native-folder>
. This failed withError: EISDIR: illegal operation on a directory, read
.Output:
Reproducible Demo
This is also reproducible in current
master
of facebook/react-native:The text was updated successfully, but these errors were encountered: