fileSystem.statSync is not a function
See original GitHub issueGetting this error only on v7.1.2. When I downgrade to 7.1.1 - everything works.
Module build failed: TypeError: fileSystem.statSync is not a function
at module.exports (.../node_modules/babel-loader/lib/utils/exists.js:7:25)
at find (.../node_modules/babel-loader/lib/resolve-rc.js:13:9)
at Object.module.exports (.../node_modules/babel-loader/lib/index.js:113:132)
Host node v8.1.2 Electron version is 1.7.5 webpack 3.5.5
Issue Analytics
- State:
- Created 6 years ago
- Reactions:47
- Comments:20 (4 by maintainers)
Top Results From Across the Web
fs.statSync is not a function - node.js - Stack Overflow
I'm so confused. Apparently fs.statSync in the following code is not a function... Can somebody please explain to me why the following code...
Read more >Node.js fs.statSync() Method - GeeksforGeeks
Returns: It returns a Stats object which contains the details of the file path. Below examples illustrate the fs.statSync() method in Node.js:
Read more >TypeError: fs.readFileSync is not a Function in JS | bobbyhadz
The "fs.readFileSync" is not a function error occurs when we misspell the `readFileSync` method or try to use the method in the browser....
Read more >fs-extra - npm
Start using fs-extra in your project by running `npm i fs-extra`. ... readFileSync is not a function; must use fs.readFileSync.
Read more >How to use the fs-extra.statSync function in fs-extra | Snyk
try { stats = fs.statSync(cfg.baseIconsDir); } catch (e) { failWarn('Default icons directory (' + cfg.baseIconsDir + ') was NOT found.
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
if you use webpack 1.x please use babel-loader 6.x
My temporarily solution is downgrade babel-loader to 7.1.1