Possible upgrade to node 12.x.x

[jgvictores]

Up till now, on node versions above v10.x.x (e.g. v12.22.8), we ran into:

graceful-fs/polyfills.js:287
      if (cb) cb.apply(this, arguments)
                 ^
TypeError: cb.apply is not a function

Inspired by https://www.it-swarm-es.com/es/node.js/gitbook-cli-install-error-typeerror-cb.apply-no-es-una-funcion-dentro-de-graceful-fs/818378930/, I've managed to consistently run typical commands on node v12.22.8 (for reference, [email protected]).

Preparation:

mkdir p ~/tmp
cd ~/tmp
npm install gitbook-cli
npm install gitbook
cd node_modules/npm/node_modules/
npm install [email protected]

Running commands:

~/tmp/node_modules/gitbook-cli/bin/gitbook.js install
~/tmp/node_modules/gitbook-cli/bin/gitbook.js build
~/tmp/node_modules/gitbook-cli/bin/gitbook.js serve

Notes:

• This is just an example. I understand actual changes would be forking gitbook and updating some package.json to enforce [email protected].
• https://www.it-swarm-es.com/es/node.js/gitbook-cli-install-error-typeerror-cb.apply-no-es-una-funcion-dentro-de-graceful-fs/818378930/ says graceful-fs@latest throws a specific error. In my case, 4.2.9 is installed; I get no console output error info, but running has no effect (possibly I do not have some debug flag activated).

Related:

• Upgrades in GitBook questions-and-answers#63
• Modificaciones en GitBook asrob-uc3m/actas#148
• Installation failure of plugin include-csv #1
• isaacs/node-graceful-fs@168bdb8

[jgvictores]

• This is just an example. I understand actual changes would be forking gitbook and updating some package.json to enforce [email protected].

Possibly the following (note gitbook repo, not gitbook-cli):
https://github.com/GitbookIO/gitbook/blob/6c6ef7f4af32a2977e44dd23d3feb6ebf28970f4/package.json#L34

Edit: Regarding npm on forks: https://stackoverflow.com/questions/40528053/npm-install-and-build-of-forked-github-repo

[PeterBowman]

cd node_modules/npm/node_modules/

There is something missing here, the node_modules directory appears out of nowhere. But I followed this and could successfully install gitbook on latest node Docker image (current-alpine, i.e. v17):

cd /usr/local/lib/node_modules/gitbook-cli/node_modules/npm/node_modules/
npm install [email protected] --save

[jgvictores]

There is something missing here

npm install -g installs into /usr/local/lib, I omitted the -g flag to do local tests on the relative path.

Still, this is a hack. Actually touching the gitbook package.json would be the coolest solution.