Skip to content
This repository has been archived by the owner on Jul 1, 2020. It is now read-only.

Missing data Directory on Fresh Clone. #1

Open
zrc210 opened this issue Jul 24, 2017 · 1 comment
Open

Missing data Directory on Fresh Clone. #1

zrc210 opened this issue Jul 24, 2017 · 1 comment

Comments

@zrc210
Copy link

zrc210 commented Jul 24, 2017

This is a super minor issue, but for the less technically inclined, it can introduce unnecessary barriers.

On a fresh clone, the data directory does not exist.

Executing node fetch.js all results in the following top-level exception:

Fetching projects...
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open 'data/projects.js'
    at Object.fs.openSync (fs.js:582:18)
    at Object.fs.writeFileSync (fs.js:1301:33)
    at saveProjectsToFile (/.../project-analytics/fetch.js:210:6)
    at Request._callback (/.../project-analytics/fetch.js:254:5)
    at Request.self.callback (/.../project-analytics/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:192:7)
    at Request.<anonymous> (/.../project-analytics/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)

The README.md should be updated to include the step to create the directory. Or better yet, the repository should include the empty directory, with a .gitignore.

@promethean
Copy link

I ran into the same issue

iguatemigarin pushed a commit to iguatemigarin/project-analytics that referenced this issue Mar 29, 2019
closes useshortcut#1

This commit fixes the issue of having to manually create the *data*
folder on fresh clone.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants