kriasoft / kriasoft/react-firebase-starter

node run publish gives error

Open
#129 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
4.5k
Forks
752
PR merge metrics
No merged PRs in 30d

Description

Just following the boilerplate instructions, without touching anything I get this error:

node run publish
Starting 'publish'...
Starting 'build'...
Starting 'clean'...
Finished 'clean' after 9ms
Starting 'bundle'...
Time: 10159ms
                       Asset     Size  Chunks             Chunk Names
   0.62e754d958e21f5ae018.js  4.39 kB       0  [emitted]
main.514320d4ba2398c1c451.js   502 kB       1  [emitted]  main
Finished 'bundle' after 10228ms
Starting 'html'...
Finished 'html' after 2ms
Starting 'sitemap'...
Finished 'sitemap' after 1ms
Finished 'build' after 10242ms
? Allow Firebase to collect anonymous CLI usage information? Yes
? Paste authorization code here: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Error
    at Error.FirebaseError (/Users/bernat/Dropbox/Bernat/Projects/Surf Coach/products/coacher/node_modules/firebase-tools/lib/error.js:11:17)
    at /Users/bernat/Dropbox/Bernat/Projects/Surf Coach/products/coacher/node_modules/firebase-tools/lib/requireAccess.js:45:26
    at lib$rsvp$$internal$$tryCatch (/Users/bernat/Dropbox/Bernat/Projects/Surf Coach/products/coacher/node_modules/rsvp/dist/rsvp.js:1036:16)
    at lib$rsvp$$internal$$invokeCallback (/Users/bernat/Dropbox/Bernat/Projects/Surf Coach/products/coacher/node_modules/rsvp/dist/rsvp.js:1048:17)
    at lib$rsvp$$internal$$publish (/Users/bernat/Dropbox/Bernat/Projects/Surf Coach/products/coacher/node_modules/rsvp/dist/rsvp.js:1019:11)
    at lib$rsvp$asap$$flush (/Users/bernat/Dropbox/Bernat/Projects/Surf Coach/products/coacher/node_modules/rsvp/dist/rsvp.js:1198:9)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

authorization code is XXXX

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with the boilerplate publish command, node run publish, after the build completes. Start by reading the Firebase CLI stack locations mentioned in firebase-tools/lib/requireAccess.js and firebase-tools/lib/error.js; done means the publish step no longer ends with the shown Firebase error.

Written by the indexing model from the issue text.

Assessment

Tech stack
firebase, javascript, node.js, react
Domain
cloud, devops, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.