Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Migrate to Node 10 #73

Closed
hobbyquaker opened this issue Oct 27, 2018 · 3 comments
Closed

Migrate to Node 10 #73

hobbyquaker opened this issue Oct 27, 2018 · 3 comments
Labels
🧞‍♂️build process 🚀enhancement New feature or request
Milestone
2.0

Comments

@hobbyquaker
Copy link
Member

No description provided.

@hobbyquaker hobbyquaker added the 🚀enhancement New feature or request label Oct 27, 2018
@hobbyquaker hobbyquaker added this to the 2.0 milestone Oct 27, 2018
@Sineos
Copy link

Sineos commented Oct 29, 2018

Das bedeutet dann ein npm rebuild für die 3rd party nodes, oder?

@hobbyquaker
Copy link
Member Author

Jupp, dafür muss ein Migrationsstep in den Installer der das einmalig macht und dann irgendwie persistiert dass es erledigt ist damit es nicht bei jedem Update wiederkommt. Außerdem müssen die "prebuilt" binaries (https://github.com/hobbyquaker/RedMatic/tree/master/prebuilt/armv6l) auch für Node 10 neu gebaut werden. Eilig ist es bis jetzt nicht, Node 8 hat ja aktiven Long Term Support bis April 2019.

@hobbyquaker
Copy link
Member Author

related: #88

hobbyquaker added a commit that referenced this issue Jan 10, 2019
@hobbyquaker
migrate to node 10 (#73)
549ccd9
hobbyquaker added a commit that referenced this issue Jan 10, 2019
@hobbyquaker
migrate to node 10 (#73)
e9a1f0e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🧞‍♂️build process 🚀enhancement New feature or request
Milestone
2.0
Development

No branches or pull requests
2 participants
@hobbyquaker @Sineos