-
-
Notifications
You must be signed in to change notification settings - Fork 215
Description
Bug
I encountered an installation error while following the official Self-hosted Quickstart guide (https://firecms.co/docs/self).
The create-firecms-app tool scaffolds a package.json with dependencies set to ^3.0.0, but this stable version doesn't seem to be published on npm yet, causing the installation to fail.
Steps to Reproduce
- Run the quickstart command: npx create-firecms-app@latest my-cms
- Navigate into the new directory: cd my-cms
- Attempt to install dependencies: pnpm install
Expected Behavior
The dependencies should install successfully, allowing the project to run.
Actual Behavior
The pnpm install command fails with the following error:
Analysis
The project's package.json is generated with the following dependencies:
"dependencies": {
"@firecms/core": "^3.0.0",
"@firecms/firebase": "^3.0.0",
"@firecms/ui": "^3.0.0",
...
}
The error message indicates that the latest available version is a pre-release (3.0.0-rc.2), and no stable 3.0.0 version exists. The ^3.0.0 version specifier looks for a stable version compatible with 3.0.0 and fails to find one.
Proposed Solution
The create-firecms-app template should be updated to use the latest available pre-release version in the generated package.json.
For example, changing the dependencies to:
"dependencies": {
"@firecms/core": "^3.0.0-0",
"@firecms/firebase": "^3.0.0-0",
"@firecms/ui": "^3.0.0-0",
...
}
-0 sorts before any other prerelease tag (-alpha, -beta, -rc.2, …), so ^3.0.0-0 matches 3.0.0-rc.2 now and will also accept the eventual 3.0.0 (and other 3.x releases under the caret).
This would allow new users following the quickstart guide to install the project dependencies without error.
Environment
OS: macOS
Package Manager: pnpm
(I'm using pnpm here, but I don't think this matters.)