razonyang / hugo-theme-bootstrap-comments

1 stars 0 forks source link

en/docs/installation/git-submodule/ #55

Closed utterances-bot closed 2 years ago

utterances-bot commented 2 years ago

Install via Git Submodule - Hugo Bootstrap

This article refers to the traditional installation method of cloning the theme locally as Git submodule. It describes how to install, upgrade the theme, and write new articles. While this installation method is still widely used, we recommend to install the theme as Hugo module. Installation Create a New Site from Scratch 1$ hugo new site myblog 2$ cd myblog 3$ git init 4$ git submodule add https://github.com/razonyang/hugo-theme-bootstrap themes/hugo-theme-bootstrap 5$ cp -a themes/hugo-theme-bootstrap/exampleSite/* .

https://hbs.razonyang.com/en/docs/installation/git-submodule/

MarcinKlejna commented 2 years ago

When building a site I get this error:

npm install
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! Exit handler never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://github.com/npm/cli/issues>

npm ERR! A complete log of this run can be found in:
npm ERR!     /data/data/com.termux/files/home/.npm/_logs/2022-05-03T11_15_22_089Z-debug-0.log
razonyang commented 2 years ago

@MarcinKlejna Hi, it should be the npm's issue, hope this helps:"https://github.com/npm/cli/search?q=npm+ERR%21+Exit+handler+never+called%21&type=issues.

Could you please provide the npm version you use? I'll try to reproduce this issue.

MarcinKlejna commented 2 years ago

Thank you for your willingness to help I got the error with nodejs-lts version

npm -v 8.5.0
node -v v16.14.2

As well as the newer one:

npm -v 8.5.5
node -v v17.9.0
razonyang commented 2 years ago

image

Unfortunately, I could not reproduce it with npm 8.5.5.