-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Make tests pass using Node 5 / NPM 3 #832 #840
Conversation
Make tests pass using Node 5 / NPM 3 facebook#832 Make tests pass using Node 5 / NPM 3 facebook#832 Make tests pass using Node 5 / NPM 3 facebook#832
ugh I'm having some trouble merging all these commits .. I might give up and submit a new pr |
No worries, when we merge this, it will all be combined into one commit. |
Ok cool thanks!
|
"<rootDir>/node_modules/react/", | ||
"<rootDir>/node_modules/react-dom/", | ||
"<rootDir>/node_modules/react-static-container/" | ||
"<rootDir>/node_modules/(?!(fbjs/lib/ErrorUtils.js$|fbjs/lib/fetch.js$|fbjs/lib/fetchWithRetries.js$))" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you keep the deleted lines here and just have 2 patterns and add 4
and 5
to the travis config, do the tests pass in both environments? It'd be nice to work in both if it's just adding the new patterns instead of replacing them.
Is there something that makes it difficult to keep the npm 2 patterns in this file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only difficulty is I don't know how to. Let me see what I can do
This is great, thanks for taking the extra step for cross compatibility! Just one more thing |
@@ -30,7 +30,8 @@ | |||
"dependencies": { | |||
"babel-runtime": "5.8.24", | |||
"fbjs": "^0.7.0", | |||
"react-static-container": "^1.0.0-alpha.1" | |||
"react-static-container": "^1.0.0-alpha.1", | |||
"babel-relay-plugin": "0.7.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the idea is that people would need to add babel-relay-plugin
to their project with npm 3, so it should remain (just) a peer dependency. I'd love someone with more npm knowledge here..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edit: If the plugin isn't under dependencies, you have to manually install it with npm 3.
Which means npm test
will fail in travis-ci since the plugin wasn't installed. You can see the failing tests above for one of my commits: https://travis-ci.org/facebook/relay/builds/109438390
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just guessing here, but should it maybe be in devDependencies in that case? It's needed to run the unit tests, but if you're using it in your own project, you should add it to your dependencies (to use it in your transform step).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure, let me try it out
On Fri, Feb 19, 2016 at 6:28 PM Jan Kassens notifications@github.com
wrote:
In package.json
#840 (comment):@@ -30,7 +30,8 @@
"dependencies": {
"babel-runtime": "5.8.24",
"fbjs": "^0.7.0",
- "react-static-container": "^1.0.0-alpha.1"
- "react-static-container": "^1.0.0-alpha.1",
- "babel-relay-plugin": "0.7.1"
Just guessing here, but should it maybe be in devDependencies in that
case? It's needed to run the unit tests, but if you're using it in your own
project, you should add it to your dependencies (to use it in your
transform step).—
Reply to this email directly or view it on GitHub
https://github.com/facebook/relay/pull/840/files#r53542588.
fyi jest 0.9.0 (without the fb-suffix) will have fixed npm3 support in Jest. I'll try to get it out next week :) |
@@ -92,7 +93,8 @@ | |||
"<rootDir>/node_modules/fbjs/lib/(?!(ErrorUtils.js$|fetch.js$|fetchWithRetries.js$))", | |||
"<rootDir>/node_modules/react/", | |||
"<rootDir>/node_modules/react-dom/", | |||
"<rootDir>/node_modules/react-static-container/" | |||
"<rootDir>/node_modules/react-static-container/", | |||
"<rootDir>/node_modules/(?!(fbjs/lib/ErrorUtils.js$|fbjs/lib/fetch.js$|fbjs/lib/fetchWithRetries.js$))" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you should be able to revert this change once I update to jest 0.9.0-fb3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok sure! I'll be awaiting jests 0.9.0-fb3 release
Summary:0.9.0-fb3 comes with all those sweet npm3 fixes. Also see #840 and #832. Tests are passing for me on node4 both with npm2 and npm3. See jestjs/jest@7b44ca0 and jestjs/jest@2d10421 cc kassens raineroviir Closes #877 Differential Revision: D2971806 fb-gh-sync-id: 85f2898f71df12eaf7f2b4bd6a2e641305453b45 shipit-source-id: 85f2898f71df12eaf7f2b4bd6a2e641305453b45
Looks like the flow fix didn't quite work. Sorry this is such a journey and thank you for keeping the updates coming! |
Yeah! Its a big project, not easy! We can either ignore the 'base62' node_module or include it under Flow, in the flowconfig which one makes more sense? (Both would fix the travis error) |
Getting this error on
as well as this on
Seems like ES6 Set isn't getting loaded? |
@raineroviir that's from a commit of mine yesterday, i'm trying to figure out why Set isn't available and will report back here. |
see #881 for the fix to the missing |
Thanks Mr. Savona |
Awesome, great to see it finally all working 👍 @facebook-github-bot import |
Thanks for importing. If you are an FB employee go to Phabricator to review. |
Yes! This is great. |
Glad to help =) |
0acd8e2
No description provided.