Access/fork setting, could not run locally
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github, javascript
- Domain
- developer-experience, tooling
Research direction
Start by checking the repository access and fork settings, then inspect package.json, .gitignore, and the existing package-lock.json. Reproduce the local npm failure and compare it with eresolve-report.txt. Done means maintainers resolve the access question, local setup works, and the dependency files have an agreed tracking policy.
Written by the indexing model from the issue text.
Description
OK I'm having several problems here:
- Not sure if this is my problem with the setting, but do I have writing access to this repo @kgukevin @yoelcortes ? I made some changes and tried to push, but git refused (and docs here said it could be I didn't have the permission)
-
Also forking is disabled so I couldn't fork as well. Why would we want this repo to be private?
-
Additionally, I couldn't run it locally, the error screenshot/log are attached
- Why
package.jsonis included in.gitignore? I thought we would want the dependencies info to be up to date, includingpackage-lock.jsonin.gitignoremakes sense because that'll be generated locally when runningnpm install- related, we should probably remove the existing
package-lock.jsonfile?
- related, we should probably remove the existing
Thanks!
- Dominant language
- Vue
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from BioSTEAMDevelopmentGroup/biosteam-web
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
BioSTEAMDevelopmentGroup/biosteam-web#41 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in BioSTEAMDevelopmentGroup/biosteam-web
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
block/artifact-swap#174 ·
-
app CLI enhancement TUI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3417 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apple/swift-async-algorithms#458 ·