Uncaught TypeError: utils.isStandardBrowserEnv is not a function
See original GitHub issueJust running “npm run watch” and I’m getting the error every 4-5 re-compilations.
Uncaught TypeError: utils.isStandardBrowserEnv is not a function
at Object.chars (app.js:64325)
at __webpack_require__ (app.js:20)
at Object.<anonymous> (app.js:26040)
at __webpack_require__ (app.js:20)
at getDefaultAdapter (app.js:10529)
at Object.<anonymous> (app.js:10538)
at Object.<anonymous> (app.js:10603)
at __webpack_require__ (app.js:20)
at Object.module.exports (app.js:63840)
at __webpack_require__ (app.js:20)
Everything is at the newest version
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:28 (1 by maintainers)
Top Results From Across the Web
Uncaught TypeError: utils.isStandardBrowserEnv is not a ...
Just running "npm run watch" and I'm getting the error every 4-5 re-compilations. Uncaught TypeError: utils.isStandardBrowserEnv is not a ...
Read more >npm run watch - utils.isStandardBrowserEnv - Laracasts
Uncaught TypeError : utils.isStandardBrowserEnv is not a function. So I can't watch for sass changes anymore... I found an opened issue about this...
Read more >Uncaught TypeError: utils.isStandardBrowserEnv is not a function
Just running "npm run watch" and I'm getting the error every 4-5 re-compilations. Uncaught TypeError: utils.isStandardBrowserEnv is not a function at ...
Read more >Uncaught TypeError: "utils.useControlled" is not a function
I had the same error. It was due to a version mismatch between @material-ui/core and @material-ui/lab . Precisely, you can check that ...
Read more >axe-core/axe.js - chromium/src/third_party - Git at Google
console.log('Could not create a template function: ' + str); ... throw new TypeError('executor must be a function.'); ... function isStandardBrowserEnv() {.
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
@davidhoeck is right that this has something to do with the axios library and it’s utils file, but I’m guessing the bug is still somewhere within mix’s own
watch
config.Here is a temporary fix: require/import the full axios dist file. All of it’s own internal dependencies will be included and webpack/mix won’t need to load them. The following works for me and solves this very annoying issue.
window.axios = require('axios/dist/axios.js');
Here the same problem when running npm run watch I had to stop and run again to make it work when making any sass change.