Repository navigation
(reading files issue) ENOENT: no such file or dicrectory - fs:js.640 #6911
Description
- Electron version: 1.3.3
- Operating system: Ubuntu Linux 16.04 LTS
Hi, I am trying to read a json file using NodeJS's fs module. The path is correct, but when the app runs, it could not find the file.
Here is the block of code in a file called index.js:
// index.js
const fs = window.require('fs');
const path = window.require('path');
// get configuration file
const data = fs.readFileSync(path.join(__dirname, 'config.json'), 'utf8');
const config = JSON.parse(data);
Here is my app's structure:
The BrowserWindow then responded with this:
fs:js.640 then pointed to this:
I know this sounds like a problem with NodeJS, but I got the same code working outside of the app.
I hope this can be fixed, thanks in advance! :)
Activity
vsemozhetbyt commentedon Aug 20, 2016
@shuliandre Do you use the same version of Node in Electron and in outside testing? There was some big fs fix in the last Node. BTW, is your app in somehow virtual drive? This also can cause problems for Node older than 6.4.0
enlight commentedon Aug 20, 2016
I'm guessing
__dirnameis an empty string because you're using Webpack or something like it.FYI, GitHub issues are for bug reports and feature requests, for everything else see the community.
chito256 commentedon Aug 20, 2016
@vsemozhetbyt Hi, the current version of NodeJS on my machine is 6.4.0. I'm not sure how I can check its version in Electron though, can you suggest a way for me to do it? Thanks 😄
@enlight Yes I am using Webpack, but even if I only specify the path as
path.join('config.json', 'utf8');, it still wouldn't work. And yes I knew about the Electron community, Slack is my prefered choice but I haven't used it much, I will try to use the community more often 😄 Thanks for your reply 😄chito256 commentedon Aug 20, 2016
@vsemozhetbyt Oh I checked the Node version in Electron and it's currently 6.3.0, is there a way for me to upgrade to the latest version?
vsemozhetbyt commentedon Aug 20, 2016
@shuliandre I am afraid not untill the Electron upgrade it. But we are not sure this is the issue yet. So is your app in the virtual drive?
chito256 commentedon Aug 20, 2016
@vsemozhetbyt No I am not using a virtual drive, I only use
webpack-dev-serverand start the server and the app separately (through 2 Terminal).MarshallOfSound commentedon Aug 20, 2016
@shuliandre The issue is probably due to how webpack inlines
__dirnameHowever as @enlight said
If you need help check out the discussion forums or Slack please 👍
chito256 commentedon Aug 20, 2016
@MarshallOfSound Okay, thanks for your support! 👍
MarshallOfSound commentedon Aug 20, 2016
@shuliandre FYI
webpack/webpack#1599
chito256 commentedon Aug 20, 2016
@MarshallOfSound Oh so that was the issue, this is the first time I encounter it 😄 Thanks Samuel! 👍