Comments (10)
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/88227116.
from nodejs-buildpack.
At this time, we have to discuss the testing strategy of io.js
. Since it is brand new, most of us don't have any experience with it. It is a hard fork from node
at a particular version, but there are differences in runtime and such.
Our discussion includes what integration tests we want to put around it. If we can easily take our node
tests and just use them for io.js
, then we have a good place to start.
Most importantly product needs to prioritize this for us. We'll keep this ticket updated.
from nodejs-buildpack.
Thanks for the info. My instinct is that you should just reuse your existing integration tests, there is no need to test new language features etc... as that's not part of the buildpack. The only change that should be required to test applications (or any application) wanting to use iojo is to update the package.json
file to specify an iojo
engine instead of a node
one and the merge from Heroku should take care of all of that.
from nodejs-buildpack.
I'm not sure it'll be completely straightforward. The initial io.js patch refers to a resolution service on Heroku.
To support the cached (offline) buildpack we'd need to replicate that functionality in lib/version_resolver.js
and shunt the request to semver.herokuapp.com to it.
from nodejs-buildpack.
@jtarchie @flavorjones Can we take a new look at this? It doesn't look like a lot has changed on their end to support it, we may be able to get around not pulling latest from semver and instead use latest we package in the skinny buildpack.
/cc @stubbornella
from nodejs-buildpack.
We'd love to start using and testing on io.js on CF.
from nodejs-buildpack.
Yea I'd also like to see support for io. The two forks are probably going to be merging back, but its likely that most of the changes will be coming from io. If we want to stay current its probably good to have support now. It isn't clear when they will reconcile but io seems to be where all the new development is happening now.
from nodejs-buildpack.
I've scheduled work on this -- see https://www.pivotaltracker.com/story/show/88227116 for details.
from nodejs-buildpack.
This might not be relevant now, seems that iojs is planning to merge back in to Node http://www.theregister.co.uk/2015/06/15/nodejs_iojs_project_merger/
from nodejs-buildpack.
@mhoran says:
We verified that the Node.JS and io.js code bases will be merging. The io.js project will become Node.js. Currently the merge is still in process, and the official site still links to Joyent's source. However, this should be pointing to io.js at some point in the "near" future.
We modified the buildpack to use a binary produced from the io.js source, and brats tests passed. We're not going to make the required changes to binary-builder at this point, as everything is a moving target at the moment.
See https://nodejs.org/foundation/#index_md_timeline for an outdated timeline
from nodejs-buildpack.
Related Issues (20)
- When will the default node version change? HOT 2
- **ERROR** Unable to install npm: exit status 9 HOT 2
- Typo in 1.8.3 release text HOT 1
- Correct Node v16 deprecation date
- Release: nodejs-buildpack (Feb) HOT 3
- Release: nodejs-buildpack (Mar) HOT 1
- Removal of node.js 14 from the nodejs-buildpack HOT 1
- Ruby is not available in cflinuxfs4 HOT 2
- Python is not available on the cflinuxfs4 stack HOT 1
- Release: nodejs-buildpack (Apr) HOT 1
- Problems with scanning the project
- Install bootstrapped python into buildpack-specific namespace
- Dependency Deprecation Alert HOT 4
- Release: nodejs-buildpack (May) HOT 4
- Release: nodejs-buildpack (Jun) HOT 1
- Release: nodejs-buildpack (Jul) HOT 1
- Deployment to BTP fails when Node is upgraded to v16.20.1 HOT 2
- Supply step do not retry when error is connection reset by peer HOT 4
- Release: nodejs-buildpack (Aug)
- Release: nodejs-buildpack (Sep) HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nodejs-buildpack.