-
Notifications
You must be signed in to change notification settings - Fork 359
Test out node 0.12.x with our project locally #581
Copy link
Copy link
Closed
Labels
CODESome other Code related issue and it should clearly describe what it is affecting in a comment.Some other Code related issue and it should clearly describe what it is affecting in a comment.migrationUse this to indicate that it may apply to an existing or announced migration.Use this to indicate that it may apply to an existing or announced migration.
Metadata
Metadata
Assignees
Labels
CODESome other Code related issue and it should clearly describe what it is affecting in a comment.Some other Code related issue and it should clearly describe what it is affecting in a comment.migrationUse this to indicate that it may apply to an existing or announced migration.Use this to indicate that it may apply to an existing or announced migration.
If anything fails on x64 and/or ia32, Sass (node-sass) excluded but dev should still be functional otherwise, use semver to hopefully prevent usage on our node host provider by setting a more restrictive range at /package.json#L80.
e.g.
>=0.10.32 <0.11.0or the like... v0.11.x seems to have been skipped for release.Whether or not nodejitsu respects this npm standard has yet to be determined and we won't know this until they migrate.