ReferenceError: file is not defined
See original GitHub issueI’m getting the below reference error when building my project using styleguidist. It looks like the console logging that occurs in the catch block of props.loader.js is referencing a file
variable that is declared in a different block. This could probably be fixed by initializing file
as a var outside the try
block scope.
Module build failed: ReferenceError: file is not defined
at Object.module.exports (<snip>/node_modules/react-styleguidist/loaders/props.loader.js:40:66)
❯ node -v
v6.5.0
❯ npm -v
3.10.7
❯ cat package.json | grep version
"version": "3.1.1"
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:5 (2 by maintainers)
Top Results From Across the Web
"File is not defined" error in javascript while executing from ...
It is because the variable File is not defined. So you are trying to do new File(txtFile) but there is nothing that defines...
Read more >ReferenceError: file is not defined - JavaScript - SitePoint
Hi, Following is my code, var assert = require('assert'); const path = require("path"); const fs = require("fs"); ...
Read more >ReferenceError: file is not defined : r/learnjavascript - Reddit
Hi, Following is my code, var assert = require('assert'); const path = require("path"); const fs = require("fs"); //const F5 =…
Read more >FilePicker.js: "File is not defined" after selecting file to upload
It is reproducible on this and at least one other site with a file upload field. ... This no longer works. Expected results:...
Read more >ReferenceError: require is not defined in JavaScript - Stack Diary
The "ReferenceError: require is not defined" error occurs when the require function is used in a JavaScript file that is intended to be ......
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
Ah, I see that this was fixed in #173, but it has not been released to npm yet. Could we publish a new version to npm?
4.0.0 is out!