Create firecms-app fails

[botzyus]

Hi there,

I'm trying to create a firecms app using both commands: yarn create firecms-app and npm create firecms-app gives the same error:
Error loading projects
Error getting projects {
message: 'Request had insufficient authentication scopes.',
code: 'google-api-not-enabled',
data: {}
}
MacOS : 15.3
node -v
v22.14.0

firebase -V
13.31.1

I 'm owner of the google project selected, logged in, also for firebase project owner and also logged in.
Can you please specify what are the scopes that I'm missing?
Thank you.

[marianmoldovan]

Hello @botzyus,

Can you try enabling the Firebase Management API in your Google Cloud Console?

Here are the instructions to do so: https://cloud.google.com/endpoints/docs/openapi/enable-api

If needed, you can safely delete the ~/.firecms folder and log in again.

Let us know.

[botzyus]

Hi @marianmoldovan,

Already have Firebase Management API enabled.
I managed to get the firecms to be installed on my local by copying from github zip, the folder: packages/cli/templates/template and running yarn install.

When I run yarn dev to start the cms on local, I got almost the same error as u got here: #686

My error:
"
✘ [ERROR] No matching export in "node_modules/@tiptap/pm/view/dist/index.js" for import "__serializeForClipboard"

node_modules/@firecms/editor/dist/index.es.js:33:71:
  33 │ import { DecorationSet as DecorationSet$1, Decoration as Decoration$1, __serializeForClipboard } from "@tiptap/pm/view";

"

Was not able to fix it adding dependencies: "prosemirror-view": "^1.37.2" and running yarn install again after deleting node_modules/ and yarn.lock

Any thoughts how I can fix the issue?

[marianmoldovan]

Hello @botzyus ,

We are currently fixing an issue, but if you want to sort it out meanwhile, you can follow this steps:

1. Install firecms cli from npm, npm install -g firecms
2. Create a project like usual, firecms init. Or use the one you already have
3. Add the "prosemirror-view": "1.37.2" in your package.json
4. Remove package-lock.json and node_modules
5. npm i

And running npm run dev or npm run build should be fine for now.

Can you please try again?

[botzyus]

Hello @marianmoldovan ,

Using npm was the solution, thanks.