-
Notifications
You must be signed in to change notification settings - Fork 577
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
Missing dependencies #2259
Comments
Also these should be dependencies not devDependencies: (required in scripts/download-realm.js)
|
@arnebr @shenjunru I haven't been able to reproduce it from a fresh project (see the attached screenshot):
Moreover, first building a project with v2.23.0 and then upgrade to v2.24.0 also works fine. When looking at Btw, I am using node v10.13.0 and yarn v1.13.0. |
Indeed in a clean space it works fine, don´t know what happend here then. Sry for bothering. |
@shenjunru As I outlined, I did try with |
Could you check listed packages exist in the project node_modules, not out of project.
|
I'm having the same issue w/ npm 6.7.0, upgrading from realm@2.21.1 in an existing project. |
I too got the error:
|
We currently don't support node.js v11. Please try again using node.js v10 or v8. |
@HolySamosa Upgrading to v2.24.0 brings many new things so you might have to clean your workspace. Did you clean your workspace before building? |
Found issue. In v2.24.0, The Xcode project will run I think those are not good behaviors.
I also wrote a shell script |
@shenjunru I have tried with the exact same versions as you, and the modules are installed. |
I can confirm that I get this on version 2.24.0 but I don't get this when I change my |
@shenjunru It's a good shell script. The reason we wrote it in JS originally was that we also need it on Windows. The shell script within Xcode is using a particular version of node. The issue here is that if you have multiple versions of node installed, Xcode will pick the default version. Xcode is spawning a new login shell, and therefore it doesn't inherit the settings from any shell. |
I'm happy to report that I'm no longer seeing this issue w/ v2.25.0. :-) |
I don't have this bug on my machine, but one of my workmate had this issue when compiling our project with He had to add these modules to our "command-line-args": "^5.1.1",
"decompress": "^4.2.0", |
@StevenMasini We moved those dependencies in v2.26.0 so if you upgrade, it should have been solved. |
I added a issue related to this |
hey guys, you just need to |
Goals
Try to run and build the new version 2.24.0.
Expected Results
The build process should download the new coca and decompress and unzip it.
Actual Results and Workaround
The packages "decompress" and "https-proxy-agent" are missing.
It works if you do
Steps to Reproduce
Try to install the new version.
Version of Realm and Tooling
React Native Environment Info:
System:
OS: macOS 10.14.3
CPU: (4) x64 Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
Memory: 31.00 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.11.0 - /usr/local/bin/node
Yarn: 1.3.2 - ~/.yarn/bin/yarn
npm: 6.8.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 22, 23, 25
Build Tools: 23.0.1, 23.0.2, 25.0.0, 25.0.1, 25.0.2
System Images: android-22 | Google APIs Intel x86 Atom, android-23 | ARM EABI v7a
IDEs:
Android Studio: 3.0 AI-171.4443003
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: 0.58.5 => 0.58.5
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-camera: 0.8.0
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
The text was updated successfully, but these errors were encountered: