-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Error during plugin restore: Cannot find module 'tostr' #89
Comments
I've not been able to reliably reproduce this, which leads me to believe a race condition may be involved between the Cordova hooks which are executed on running |
I've added a workaround which should cause the |
Nice, I hope it will fix the issue. I'm steadily reproducing this on my project base on this starter kit which use Ionic, if you need a test base. |
Should be fixed in |
Don't work with 3.1.0. |
Just to chime in, using 3.1.2 and also seeing this issue:
Haven't figured out how to do this in CI, but I just run |
This seems to still be an issue in |
+1, getting it too. Can somebody shed some light on this? |
TL;DR I would recommend upgrading to Your options are:
Explanation This issue occurs due to a race condition when installing Until the release of cordova-fetch with The latest version of Cordova CLI uses I can foresee a future ( |
Hello,
Each time I try to restore this plugin using a
cordova prepare
command, I get this error:cordova-custom-config: Error loading dependencies (Cannot find module 'tostr') - attempting to resolve cordova-custom-config: npm dependencies missing - installing cordova-custom-config: Installed npm dependencies
The thing is, the dependency
toatr
does not get installed even though it says so and crash the build. If I install it manually, I have no issues, so it seems like there is an issue with your npm install script?This is quite problematic on my CI build, for now I have a workaround executing
npm install tostr
after thecordova prepare
command, but it's not quite right.Could you look into this issue?
Thanks!
My env:
The text was updated successfully, but these errors were encountered: