json-schema-org / json-schema-org/ecosystem
fix: auto-create data/ directory in DataRecorder to prevent ENOENT on fresh clone
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Running npm run start on a fresh clone fails with:
Error: ENOENT: no such file or directory, open './data/initialTopicRepoData-.csv'
This happens because dataRecorder.js tries to write a CSV file to ./data/ which doesn't exist in the repo.
Steps to Reproduce
- Clone the repo fresh
- Set up
.envwithGITHUB_TOKENandTOPIC - Run
npm run startinsideprojects/initial-data/ - Observe the crash
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in projects/initial-data/dataRecorder.js and trace the CSV write triggered by npm run start. Verify the fresh-clone setup with the stated environment variables; done means the data directory is available automatically, startup no longer fails with ENOENT, and the CSV file is created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100