-
Notifications
You must be signed in to change notification settings - Fork 0
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
Updated package should solve most issues #30
Labels
Comments
Hi, sadly i get following error when i try to install:
Installing “particle-dev-local-compiler@0.1.0” failed.Hide output… <>
npm WARN engine sb-exec@3.1.0: wanted: {"node":">=6.0.0"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm WARN engine strip-bom-buf@1.0.0: wanted: {"node":">=4"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm ERR! Darwin 16.5.0
npm ERR! argv "/Applications/Particle Dev.app/Contents/Resources/app/apm/bin/node" "/Applications/Particle Dev.app/Contents/Resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/Users/Rafael/.particledev/.apm/.apmrc" "--userconfig" "/Users/Rafael/.particledev/.apmrc" "install" "/private/var/folders/rs/fzjnnw_d73n3m99zlk6zw1n80000gp/T/d-11745-11757-9bgy8q/package.tgz" "--target=0.36.8" "--arch=x64"
npm ERR! node v0.10.40
npm ERR! npm v2.13.3
npm ERR! code ENOTSUP
npm ERR! notsup Unsupported
npm ERR! notsup Not compatible with your version of node/npm: docker-compose-tool@0.0.1
npm ERR! notsup Required: {"node":">= 6.2"}
npm ERR! notsup Actual: {"npm":"2.13.3","node":"0.10.40"}
npm ERR! Please include the following file with any support request:
npm ERR! /private/var/folders/rs/fzjnnw_d73n3m99zlk6zw1n80000gp/T/apm-install-dir-11745-11757-1xd5mcb/npm-debug.log
already installed particle Dev again, updated to node v6.10.3. - I am on OS X 10.12.4
Regards Rafael
rafael mäuer | portfolio <http://www.rafaelmaeuer.de/> | linkedin <https://www.linkedin.com/in/rafael-m%C3%A4uer-84054610b> | vimeo <https://vimeo.com/rafael91>
creative developer | software engineer
… Am 05.05.2017 um 13:27 schrieb Wojtek Siudzinski ***@***.***>:
There's a latest version of local compiler package (0.1.0) which supports new buildpack format. It should fix most of the issues you all reported. Give it a go if you want!
/cc: @steelydev <https://github.com/steelydev> @unseenshadow2 <https://github.com/unseenshadow2> @LukeUSMC <https://github.com/LukeUSMC> @nanodust <https://github.com/nanodust> @csoulakian <https://github.com/csoulakian> @mfogel <https://github.com/mfogel> @mjoelmendes <https://github.com/mjoelmendes> @kasperkamperman <https://github.com/kasperkamperman> @yostinso <https://github.com/yostinso> @rafaelmaeuer <https://github.com/rafaelmaeuer> @Zuph <https://github.com/Zuph> @robertdolca <https://github.com/robertdolca> @rei-vilo <https://github.com/rei-vilo> @mikey0000 <https://github.com/mikey0000>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#30>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGHwG6l73DxRuHyuIM1MW0msjLevK_dgks5r2wetgaJpZM4NRy_6>.
|
Oh this might be caused by Particle Dev App bundling with Node 5.1.1. Could you try installing the package in Atom? We'll update the app next week so it will contain more recent Node version. |
Any update? Thank you! |
Hi Rei, sorry but we're focused on our cloud compiler recently. We'll try to get back to this asap |
Thank you for the update. Good luck with the development. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's a latest version of local compiler package (0.1.0) which supports new buildpack format. It should fix most of the issues you all reported. Give it a go if you want!
/cc: @steelydev @unseenshadow2 @LukeUSMC @nanodust @csoulakian @mfogel @mjoelmendes @kasperkamperman @yostinso @rafaelmaeuer @Zuph @robertdolca @rei-vilo @mikey0000
The text was updated successfully, but these errors were encountered: