Missing module
See original GitHub issueI’m having trouble replicating your steps. I’ve tried multiple times, and it looks like something with webpack is malfunctioning. It’s preventing me from compiling my work:
/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/webpack-cli/bin/cli.js:74
throw err;
^
Error: Cannot find module './node_modules/gas-webpack-plugin/node_modules/gas-entry-generator'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:668:15)
at Function.Module._load (internal/modules/cjs/loader.js:591:27)
at Module.require (internal/modules/cjs/loader.js:723:19)
at require (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.<anonymous> (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/gas-webpack-plugin/index.js:3:27)
at Module._compile (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10)
at Module.load (internal/modules/cjs/loader.js:685:32)
at Function.Module._load (internal/modules/cjs/loader.js:620:12)
at Module.require (internal/modules/cjs/loader.js:723:19)
at require (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.<anonymous> (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/webpack.config.js:13:19)
at Module._compile (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/v8-compile-cache/v8-compile-cache.js:178:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10)
at Module.load (internal/modules/cjs/loader.js:685:32)
at Function.Module._load (internal/modules/cjs/loader.js:620:12)
at Module.require (internal/modules/cjs/loader.js:723:19)
at require (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at WEBPACK_OPTIONS (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/webpack-cli/bin/utils/convert-argv.js:115:13)
at requireConfig (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/webpack-cli/bin/utils/convert-argv.js:117:6)
at /Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/webpack-cli/bin/utils/convert-argv.js:124:17
at Array.forEach (<anonymous>)
at module.exports (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/webpack-cli/bin/utils/convert-argv.js:122:15)
at yargs.parse (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/webpack-cli/bin/cli.js:71:45)
at Object.parse (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/yargs/yargs.js:567:18)
at /Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/webpack-cli/bin/cli.js:49:8
at Object.<anonymous> (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/webpack-cli/bin/cli.js:368:3)
at Module._compile (internal/modules/cjs/loader.js:816:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10)
at Module.load (internal/modules/cjs/loader.js:685:32)
at Function.Module._load (internal/modules/cjs/loader.js:620:12)
at Module.require (internal/modules/cjs/loader.js:723:19)
at require (internal/modules/cjs/helpers.js:14:16)
at Object.<anonymous> (/Users/pdavisjones/Documents/Coding/apps-script/honeybee4/node_modules/webpack/bin/webpack.js:156:2)
at Module._compile (internal/modules/cjs/loader.js:816:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! apps-script-starter@3.4.1 build: `webpack`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the apps-script-starter@3.4.1 build 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! /Users/pdavisjones/.npm/_logs/2019-05-17T22_36_22_012Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! apps-script-starter@3.4.1 deploy: `npm run build && npm run upload`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the apps-script-starter@3.4.1 deploy 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! /Users/pdavisjones/.npm/_logs/2019-05-17T22_36_22_037Z-debug.log
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
missing module
This module lists modules that are activated in your database but missing from your file system. These can greatly impact the performance of ......
Read more >Missing module source - python
Sometimes just quitting and reopneing VS Code helps. I know it's weird but it works for me for these errors sometimes so give...
Read more >Windows 10 Missing Module
I've been getting a pop up that says "there was a problem starting C:\PROGRA~1\COMMON~1\System\SysMenu.dll the specified module could not be ...
Read more >Error: Missing module "myNamespace" for path ...
The issue seems to occur when changing the name of a namespaced module while analysing the store with the dev tools. I'm working...
Read more >missing-module-docstring / C0114 - Pylint 2.16.0-dev ...
Empty modules do not require a docstring. Problematic code: import sys # [missing-module-docstring] def print_python_version ...
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 had to change webpack.config.js and add brackets around CleanWebpackPlugin :
const { CleanWebpackPlugin } = require('clean-webpack-plugin’);
All working well now. Thank you.
Thanks!