TypeError: __webpack_require__(...) is not a function
See original GitHub issuegetting this error on google cloud instance
TypeError: __webpack_require__(...) is not a function
at Function.requireEnsure [as e] (/srv/dist/server.js:142734:49)
line 142734
var chunk = __webpack_require__(421)("./" + ({"components-_admin-admin-module-ngfactory":
"components-_admin-admin-module-ngfactory"}[chunkId]||chunkId) + ".js");
What is the expected behavior?
Everything is working fine w/ new angualrfire auth-guards + v8 import-style lazy-loaded routes/modules, just getting this error (as well as #1169).
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:11 (4 by maintainers)
Top Results From Across the Web
TypeError: __webpack_require__.i(...) is not a function
This error can arise if you try to import something from an existing npm package (in node_modules ) but the imported thing doesn't...
Read more >TypeError: __webpack_require__(...) is not a function #9379
is not a function If the current behavior is a bug, please provide the steps to ... webpack.config.js const path = require('path'); ...
Read more >TypeError: require(...) is not a function in Node.js | bobbyhadz
To solve the "TypeError: require(...) is not a function", make sure to place a semicolon between your require call and an immediately invoked...
Read more >Module Methods - webpack
require.ensure() is specific to webpack and superseded by import() . ... Split out the given dependencies to a separate bundle that will be...
Read more >__webpack_require__ is not a function - You.com | The ...
TypeError : __webpack_require__.i (...) is not a function ... Since core is a folder of your app and not an npm module, Webpack...
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 Free
Top 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
This seems a problem with angularfire. We are going to follow up with them.
Till then the workaround is to remove
--bundleDependencies all
from package.jsonThis issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.