Closed paragonx9 closed 6 years ago
Again this very likely means that there is a dependency that's way too new. Try locking down everything in the package to the specific version listed, since that's what it was built with.
Can you pack all in a docker container?
On Oct 26, 2017 8:14 AM, "Kyle J. Kemp" notifications@github.com wrote:
Again this very likely means that there is a dependency that's way too new. Try locking down everything in the package to the specific version listed, since that's what it was built with.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/seiyria/tournamentmango/issues/145#issuecomment-339632959, or mute the thread https://github.com/notifications/unsubscribe-auth/AAvc0Cww8g3kj57-T-yGiJbd_NuJvjTdks5swGmQgaJpZM4QHBrM .
I probably could, but I don't work on this anymore. If I were to do anything with this app, it would be a rewrite. You're free to make a pull request though.
Fixed it by locking them down like you said! Feel free to delete this issue since it's pretty isolated... thanks for the help 👍
After successfully running tournamentmango on my windows machine, I tried setting it up on an Ubuntu 16.04 machine with no avail. npm install runs with no errors. When I run gulp I get the following:
I've been trying to fix this for a few hours, but I can't seem to make this work :( I've manually installed babel, babel-core, babel-register, etc. using npm but the issue won't go away. Any help is appreciated.