4 ms·
What sort of compatibility issues? Most packages update to work with new Node releases fairly quickly. Usually the packages that have compatibility issues are o
by dhritzkiv 11y ago
What sort of compatibility issues? Most packages update to work with new Node releases fairly quickly. Usually the packages that have compatibility issues are ones with native C++ bindings. If you `npm rm` the package and reinstall it, it will usually build correctly for the latest Node/V8 release.
Further, if you have a project that for whatever reason is not feasible to update to run on modern Current Node, you can use `nvm` or `n` to choose which Node release you want to use: i.e. `nvm exec 0.12 node old-project.js` and `nvm exec 6.0 node fresh-project.js`. v6 (and the versions that preceded it) has made Javascript really enjoyable to write.
- Macha 11y agoOur biggest issue is to get off node 0.12, we need to get off protractor 2, and some of our protractor tests fail on protractor 3 for reasons no one has yet figured out. The only clue is a note saying selenium webdriver 2.48 changed how its control flow worked, but nowhere is what changed from 2.47 to 2.48 documented.
- Havvy 10y agoYou can't diff between 2.47 and 2.48 and see what changed? Or is that a binary part you don't have source access to?
- Macha 10y ago"Showing 930 changed files with 13,029 additions and 10,187 deletions. " Feel free to try: https://github.com/SeleniumHQ/selenium/compare/selenium-2.47.0...selenium-2.48.2?expand=1 https://github.com/SeleniumHQ/selenium/compare/selenium-2.47... It's a dependency of a dependency with multiple language versions in the one repository.
- therealmarv 11y agothanks, I will look deeper into it. I could not install certain packages even with a fresh and clean new node.js. NVM is not the issue (I know node version handlers like nvm or tj/n). I just wondered if I'm the only one who had this compatibility issues.