-
Notifications
You must be signed in to change notification settings - Fork 29.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
6.3.1 src tarball: missing files and directories #7872
Comments
I think this was done intentionally awhile back in an effort to reduce the distributed tarball size. You will need to checkout the git repo to build docs and the like. |
:( - wondering who cares about 1-2 MB these days ... Anyway, shouldn't it be documented somewhere? |
So...how does one do this "git repo" thing to "build docs and the like" to resolve this issue? |
Running It’s probably easier and works just as well to just run |
had to go to folder with git.py in it and typed "c:\python27\python.exe git.py clone https://github.com/nodejs/node.git" and something happened without any output in the console. npm install didn't begin to work at that point. how do I "run npm install in the tools/doc/ directory of the tartball"? I can't any such folder. Is there a way to just download this thing without those missing files by chance? |
@lungbubble you should not have to use python to clone the repo do you have git installed? you can get git here. Once you have git installed you can use the command that was mentioned above If you want to learn more about git you can read this intro |
Ty, I installed the git clone, typed that in program files\nodejs and it did a bunch of stuff. Then I typed npm install npm -g (also just npm install). This was the result I got: npm ERR! not a package c:\program files\nodejs\npm npm ERR! enoent ENOENT: no such file or directory, open 'C:\users\MyUser\AppData\Local\Temp\npm-8488-242c2023\unpack-845689f2\package.json' I have no idea why its checking for files in my app data/local stuff as npm is in my program files\nodejs. |
@lungbubble let's step back for a moment. what is your ultimate goal? what are you trying to do? get a local copy of On Sun, Aug 7, 2016, 2:16 PM lungbubble [email protected] wrote:
|
We did a distinction between a developer and user. If you want to e.g. generate documentation instead of using the one that is generate for you, or for instance invoke |
I'm trying to run a python script which states I need to run "grunt build" before running the script. From what I've read (i've gone through so much stuff now, I might be missing a piece or two) I need to install nodejs to do the grunt build. So I'm just trying to install nodejs so that I can use "grunt build" so I can run the script I have. |
@lungbubble it would appear you are heading down the wrong path. If you would like to install node please follow the instructions found at --> http://nodejs.org/download/ |
Run `npm install` before building the documentation from release tarballs. The doctool currently depends on `js-yaml`, which is imported from the `tools/eslint` subtree; however, release tarballs don’t contain that directory. Running `npm install` is clearly not a beautiful solution, but it works. Fixes: nodejs#7872
Run `npm install` before building the documentation from release tarballs. The doctool currently depends on `js-yaml`, which is imported from the `tools/eslint` subtree; however, release tarballs don’t contain that directory. Running `npm install` is clearly not a beautiful solution, but it works. Fixes: #7872 PR-URL: #8413 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]>
Run `npm install` before building the documentation from release tarballs. The doctool currently depends on `js-yaml`, which is imported from the `tools/eslint` subtree; however, release tarballs don’t contain that directory. Running `npm install` is clearly not a beautiful solution, but it works. Fixes: #7872 PR-URL: #8413 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]>
Run `npm install` before building the documentation from release tarballs. The doctool currently depends on `js-yaml`, which is imported from the `tools/eslint` subtree; however, release tarballs don’t contain that directory. Running `npm install` is clearly not a beautiful solution, but it works. Fixes: #7872 PR-URL: #8413 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]>
Run `npm install` before building the documentation from release tarballs. The doctool currently depends on `js-yaml`, which is imported from the `tools/eslint` subtree; however, release tarballs don’t contain that directory. Running `npm install` is clearly not a beautiful solution, but it works. Fixes: #7872 PR-URL: #8413 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]>
Run `npm install` before building the documentation from release tarballs. The doctool currently depends on `js-yaml`, which is imported from the `tools/eslint` subtree; however, release tarballs don’t contain that directory. Running `npm install` is clearly not a beautiful solution, but it works. Fixes: #7872 PR-URL: #8413 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell <[email protected]>
https://nodejs.org/dist/v6.3.1/node-v6.3.1.tar.[gx]z source tar balls seems to be screwed up: e.g.
tools/{osx-pkg.pmdoc,pkgsrc,eslint,eslint-rules}/ are missing, whereby at least the latter 2 in turn break doc building:
The text was updated successfully, but these errors were encountered: