firecrawl / firecrawl/open-lovable
Lockfile inconsistency : package-lock.json and pnpm-lock.yaml both present
- Dominant language
- TypeScript
- Stars
- 28.4k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description :
I noticed that the repo has both package-lock.json (npm) and pnpm-lock.yaml (pnpm). The README only shows npm install, so it’s not clear which package manager should be used.
Steps to reproduce :
1) Clone the repo
2) Check the root folder
3) You’ll see both lockfiles there
Why it might be a problem :
1) Different people might install dependencies with different tools
2) Could lead to inconsistent dependency trees or harder-to-reproduce builds
Suggestion:
Pick one package manager (npm or pnpm), remove the other lockfile, and update the README if needed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the README's installation instructions and inspecting package-lock.json and pnpm-lock.yaml in the repository root. Confirm which package manager the project intends to support, then ensure only its lockfile remains and the README matches that choice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, documentation
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100