| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This should be 'tools/doc'
Sorry for confusion
Sorry, something went wrong.
|
No problem at all. Changed the commit, commit message, and PR title. That work? |
Sorry, something went wrong.
|
@RichardLitt it seems like I may have not properly identified the issue it seems that there is already a tools/doc/node_modules (I had thought I checked before opening the issue but was mistaken) The issue appears to be extra files getting added during make test and those showing up in the git diff attached is an image of this, best I could do as this happened on other systems I'm not sure that this approach with the git ignore is the correct solution, sorry about that. That being said we should use this PR to find the correct solution 😄 I'll update when I can dig in a bit more. Perhaps you can get this to repro on your machine |
Sorry, something went wrong.
|
About the node_modules: I think we should ignore the tools/doc/node_modules folder, but add back (!) the subfolders/files that we checked into the source code. As for the package-lock.json...I think we should actually commit that into the source? Also cc @refack |
Sorry, something went wrong.
There was a problem hiding this comment.
So I think this should be
tools/doc/node_modules/* !tools/doc/node_modules/.bin/marked !tools/doc/node_modules/js-yaml/index.js !tools/doc/node_modules/marked
And commit the package-lock.json into the source instead of ignoring it.
Sorry, something went wrong.
|
I edited the commit to include @joyeecheung's suggestions. I also committed the package-lock.json file. Should be good? |
Sorry, something went wrong.
|
I'll take a look, but IMHO if everything is published to npm, removing tools/doc/node_modules and adding package-lock.json is the optimal situation. That might require changing the tests to detect an offline scenario. |
Sorry, something went wrong.
|
@RichardLitt I pushed a suggested change to this PR. Feel free to remove it. |
Sorry, something went wrong.
|
Can't think of a reason to remove it, @refack. No need for every commit in this PR to come from me. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Sorry, something went wrong.
|
There is also a change in a tracked file: modified: tools/doc/node_modules/js-yaml/index.js Ignore the test/fixtures/failcounter.js it is added by me 😄 |
Sorry, something went wrong.
|
@Bamieh did you test with this patch? It should take care of this (actually unneeded) file modification. |
Sorry, something went wrong.
|
@refack yes i did run the tests and everything is in order On branch feat/add-files-to-gitignore Your branch is up-to-date with 'RichardLitt/feat/add-files-to-gitignore'. nothing to commit, working tree clean |
Sorry, something went wrong.
|
Tbh, I don't think we should be running npm install in the first place... this change just works around that issue it seems? |
Sorry, something went wrong.
|
@addaleax while I agree, I don't think we yet have consensus on removing npm install, and in the mean time this is creating friction with the test suite |
Sorry, something went wrong.
|
I'm thinking of landing this tomorrow morning, then start working on a new PR for further improvements. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
PR-URL: nodejs#17224 Fixes: nodejs#17216 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
|
\o/ thanks! Super cool. Thank you Myles for the tweet.
On Fri, Nov 24, 2017 at 10:29 AM Refael Ackermann ***@***.***> wrote:
Merged #17224 <#17224>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17224 (comment)>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AA3loYIHTXmzcvi4qAZDIQMEfOadubcpks5s5uBhgaJpZM4QnCpa>
.
--
Richard | @richlitt <https://twitter.com/richlitt> | burntfen.com
<http://www.burntfen.com>
|
Sorry, something went wrong.
| "devDependencies": { | ||
| "js-yaml": "^3.5.2" | ||
| }, | ||
| "devDependencies": {}, |
There was a problem hiding this comment.
Why this change? js-yaml is a full dependency of the doctool
Sorry, something went wrong.
There was a problem hiding this comment.
At some point it you hooked js-yaml to redirect to the copy that is in ESLint.
node/tools/doc/node_modules/js-yaml/index.js
Lines 1 to 15 in bb44626
Sorry, something went wrong.
There was a problem hiding this comment.
Yes, not running npm i is the fix here. It’s too bad the plans for releasing the doctool as a standalone module didn’t get anywhere so far, but semantically this is backwards :(
Sorry, something went wrong.
There was a problem hiding this comment.
I agree. I'll roll this back as soon as I finish testing the install-les make target.
Sorry, something went wrong.
PR-URL: #17224 Fixes: #17216 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
PR-URL: #17224 Fixes: #17216 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
PR-URL: #17224 Fixes: #17216 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
|
Had to pull this into v8.9.4 as the lack of it was breaking the macOS doc-upload build job. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This closes #17216 by adding some files to the gitignore which stick around after an aborted build. It is meant as a temporary fix.
Checklist
Affected core subsystem(s)
.gitignore, but related to docs.