You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are client errors preventing us from reaching the main menu. Based on checking out one commit at a time and rebuilding, I believe this started happening in 63cc664 (Part of linting changes in #24 .
In c4d3352, just before #15 was merged, the app will start as expected when accessing http://localhost:3000 after running docker compose up. This is because despite process.env being empty, the following code succeeds:
Looks like this is related to yarn build:app, which expects FIREBASE_URL to be available as an environment variable when called. In the short term, we can instead run FIREBASE_URL=<my-firebase-url> yarn build:app, but we may want to further improve the ergonomics around envify.
Edit: This is specifically caused by the removal of the default Firebase URL in config/development.json, which was previously set to https://duelyst-development.firebaseio.com/.
willroberts
changed the title
[APP] Regression in frontend when accessing process.env.FIREBASE_URL
[APP] Regression in frontend when using Backbone.Firebase
Sep 13, 2022
willroberts
changed the title
[APP] Regression in frontend when using Backbone.Firebase
[APP] Regression in frontend when using Backbone
Sep 13, 2022
willroberts
changed the title
[APP] Regression in frontend when using Backbone
[APP] Regression in frontend when initializing Backbone
Sep 13, 2022
Description
There are client errors preventing us from reaching the main menu. Based on checking out one commit at a time and rebuilding, I believe this started happening in 63cc664 (Part of linting changes in #24 .
The old description below was resolved in #30
Old Description (process.env.FIREBASE_URL issue)
In c4d3352, just before #15 was merged, the app will start as expected when accessing
http://localhost:3000
after runningdocker compose up
. This is because despiteprocess.env
being empty, the following code succeeds:After #15, this results in an error when loading the client:
The text was updated successfully, but these errors were encountered: