build fails for v5-beta1 because build folder is missing
See original GitHub issueWhen installing v5-beta1 via npm
and try to build it by npm run dist
some errors occurred. Mostly related because the build/
directory is missing and so the files build-plugins.js
and rollup.config.js
.
Operating system: Windows 10
Installation:
$ npm install bootstrap@next
$ cd node_modules/bootstrap/
$ npm install
$ npm run dist
Errors:
...
> bootstrap@5.0.0-beta1 js-compile-standalone-esm C:\...\Bootstrap\node_modules\bootstrap
> rollup --environment ESM:true,BUNDLE:false --config build/rollup.config.js --sourcemap
internal/modules/cjs/loader.js:968
throw err;
^
Error: Cannot find module 'C:\...\Bootstrap\node_modules\bootstrap\build\build-plugins.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:965:15)
at Function.Module._load (internal/modules/cjs/loader.js:841:27)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bootstrap@5.0.0-beta1 js-compile-plugins: `node build/build-plugins.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bootstrap@5.0.0-beta1 js-compile-plugins script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dkern\AppData\Roaming\npm-cache\_logs\2021-01-07T13_53_04_468Z-debug.log
[!] Error: Could not resolve entry module (build\rollup.config.js).
Error: Could not resolve entry module (build\rollup.config.js).
at error (C:\...\Bootstrap\node_modules\bootstrap\node_modules\rollup\dist\shared\rollup.js:5265:30)
at ModuleLoader.loadEntryModule (C:\...\Bootstrap\node_modules\bootstrap\node_modules\rollup\dist\shared\rollup.js:18470:20)
at async Promise.all (index 0)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
[!] Error: Could not resolve entry module (build\rollup.config.js).
npm ERR! bootstrap@5.0.0-beta1 js-compile-bundle: `rollup --environment BUNDLE:true --config build/rollup.config.js --sourcemap`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bootstrap@5.0.0-beta1 js-compile-bundle script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Error: Could not resolve entry module (build\rollup.config.js).
at error (C:\...\Bootstrap\node_modules\bootstrap\node_modules\rollup\dist\shared\rollup.js:5265:30)
at ModuleLoader.loadEntryModule (C:\...\Bootstrap\node_modules\bootstrap\node_modules\rollup\dist\shared\rollup.js:18470:20)
at async Promise.all (index 0)
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dkern\AppData\Roaming\npm-cache\_logs\2021-01-07T13_53_04_525Z-debug.log
npm[!] Error: Could not resolve entry module (build\rollup.config.js).
ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bootstrap@5.0.0-beta1 js-compile-standalone: `rollup --environment BUNDLE:false --config build/rollup.config.js --sourcemap`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bootstrap@5.0.0-beta1 js-compile-standalone script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Error: Could not resolve entry module (build\rollup.config.js).
at error (C:\...\Bootstrap\node_modules\bootstrap\node_modules\rollup\dist\shared\rollup.js:5265:30)
at ModuleLoader.loadEntryModule (C:\...\Bootstrap\node_modules\bootstrap\node_modules\rollup\dist\shared\rollup.js:18470:20)
at async Promise.all (index 0)
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dkern\AppData\Roaming\npm-cache\_logs\2021-01-07T13_53_04_541Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bootstrap@5.0.0-beta1 js-compile-standalone-esm: `rollup --environment ESM:true,BUNDLE:false --config build/rollup.config.js --sourcemap`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bootstrap@5.0.0-beta1 js-compile-standalone-esm script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dkern\AppData\Roaming\npm-cache\_logs\2021-01-07T13_53_04_558Z-debug.log
ERROR: "js-compile-plugins" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bootstrap@5.0.0-beta1 js-compile: `npm-run-all --parallel js-compile-*`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bootstrap@5.0.0-beta1 js-compile script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dkern\AppData\Roaming\npm-cache\_logs\2021-01-07T13_53_04_579Z-debug.log
ERROR: "js-compile" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bootstrap@5.0.0-beta1 js: `npm-run-all js-compile js-minify`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bootstrap@5.0.0-beta1 js script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dkern\AppData\Roaming\npm-cache\_logs\2021-01-07T13_53_04_601Z-debug.log
ERROR: "js" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bootstrap@5.0.0-beta1 dist: `npm-run-all --parallel css js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bootstrap@5.0.0-beta1 dist script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\dkern\AppData\Roaming\npm-cache\_logs\2021-01-07T13_53_04_693Z-debug.log
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Build Folder disappeared error - Arduino Forum
Hello, I'm having troubles getting a program to upload to my Duemilanove ATmega328. I receive the error message of "Build folder disappeared ......
Read more >Re-refactor author system to use Page.GetTerms after Hugo ...
Bep has fixed the Hugo bug in Page.GetTerms order for the upcoming Hugo 0.73 release. See gohugoio/hugo#7213 (comment)
Read more >QLC+ 5.0.0 Beta1 release - Q Light Controller+
On Windows you need to specify a new installation folder. v4 and v5 share the same configuration file (plugins conf mostly) so, in...
Read more >Drupal 5.0 beta 1
Welcome, ladies and gentlemen, to the most exciting beta release of Drupal yet, Drupal 5.0 beta 1! It fizzes and it whizzes so...
Read more >install.txt - Fossies
If you want to build libjpeg only as a static library, say . ... If the cjpeg test run fails with "Missing Huffman...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I agree with @dkern: https://github.com/twbs/bootstrap/issues/32719#issuecomment-757046759: This is very confusing. I understood the build page exactly as he did.
My suggestion then is to fully remove the “Build Tools” page from the docs! If I as a user want to “build” BS, this is the page I would going for (as I did). And the page even say everything I would expect, when I would want to build BS by myself. If this page is only relevant for people who want to work on the bootstap core files, this should be much more explained. I mean, the page also says:
And:
It’s still not clear to me, why this page is in the docs then, if this has nothing directly to do with working with (not for) BS and has nothing to do with customization too. I would expect something like this page to be located on GitHub then. I mean, if the first thing I hear after try to do what the page described is “You are not supposed to use things like that.”, then this page should not be located in the docs too.
Just my point …