-
-
Notifications
You must be signed in to change notification settings - Fork 847
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
expo install rnmapbox/maps NOT FOUND #1831
Comments
Have you tried |
yes I should have mentioned this. The above command gives the same error and adds: "undefined": "rnmapbox/maps#main" to package.json. @mfazekas |
% expo --version
5.3.0
% expo init rntest -t blank
% cd rntest
% expo install rnmapbox/maps#main
% cat package.json | grep mapbox
"@rnmapbox/maps": "rnmapbox/maps#main", |
Apologise for the text wall @mfazekas but I can't seem to figure this out. I’ve done % expo --version
5.3.1 (Gave v5.3.0 a try as well without success)
% node -v
v16.14.2
%npm -v
8.6.0
% expo init rntest -t blank
% cd rntest
% expo install rnmapbox/maps#main npm ERR! code 127 npm ERR! sh: yarn: command not found npm exited with non-zero code: 127 I’ve tried the following Tried (with no effect): $ npm cache clean --force
$ rm -rf node_modules
% delete package-lock.json
npm install -g npm@8.6.0
$ npm install
$ npm start |
you don't seems to have yarn installed and for now expo requires yarn because of the prepare script.
|
Thanks! this solved the issue and the package was added to my node modules without errors. Although adding the plugin to my app.json and running ios build command results in: cd ios
pod update
cd ..
expo run:ios Failed to resolve plugin for module "@rnmapbox/maps" relative to "{path to repo}" my package.json still keeps adding it as {"undefined": "rnmapbox/maps#main"} although expo install command succeeds. |
@ErikJungh the package is phasing over to a new npm package name, which is not yet deployed which might be a reason, why "@rnmapbox/maps": "github:rnmapbox/maps#main", And run |
Just got it running with expo run:ios aswell. If anyone comes across this and gets any issues with various "Module Mapbox not found" I solved it by adding this: % $RNMapboxMaps.post_install(installer) in the post install section of the podfile. |
Describe the bug
A clear and concise description of what the bug is.
Installing rnmapbox/maps results in an error even for completely new/fresh expo project.
To Reproduce
Steps to reproduce the behavior.
Please include a single standalone React Native component.
Use our BugReportTemplate screens as a starting point.
Please simplify the example as much as possible!
If it's a build/startup issue please include full steps to reproduce from
react-native init ...
Example:
expo init cd {projectname} npm install mapbox-gl expo install rnmapbox/maps OR expo install rnmapbox/maps#main OR npm install rnmapbox/maps
Expected behavior
A clear and concise description of what you expected to happen.
I expected rnmapbox to install and then by following the following guide be able to run rnmapbox in my expo app outside of the expo go app.
https://github.com/rnmapbox/maps/blob/main/plugin/install.md
Installing for example @expo/vector-icons works fine.
Actual behavior
A clear and concise description of what is currently happening.
The command fails with error msg:
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@rnmapbox%2fmaps - Not found
npm ERR! 404
npm ERR! 404 '@rnmapbox/maps@*' is not in this registry.
and
"undefined": "rnmapbox/maps"
is added to package.json
Versions (please complete the following information):
Additional context
Add any other context about the problem here.
The package had a namechange from react-native-mapbox-gl to rnmapbox in this commit 27 days ago:
90379a9
The text was updated successfully, but these errors were encountered: