-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create separate build configuration for staging #2064
Conversation
npm has a |
Hey, I noticed you changed some webpack configuration files. This can break production builds. Did you remember to run a production build locally to verify they still work? |
Yes, I did run a local build:
No errors. |
npm has a |
Hey, I noticed you changed some webpack configuration files. This can break production builds. Did you remember to run a production build locally to verify they still work? |
const dotenv = require('dotenv'); | ||
const common = require('./webpack.common.js'); | ||
|
||
const env = dotenv.config({path: path.resolve(__dirname, '../../.env.staging')}).parsed; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the only difference between prod/staging? Is there a way to DRY this up more?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DRYed up a bit 👍
Nice, this seemed to have worked 🎉 |
Details
There are many CORS errors on https://staging.expensify.cash
And it is because it is using the wrong value for the
EXPENSIFY_URL_CASH
environment variable.Fixed Issues
No issue, hot-fixing staging.
Tests
Tested with local build, which is the best we can do for now.