-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix(quasar-cli-vue3): fixed prod builds #3208
fix(quasar-cli-vue3): fixed prod builds #3208
Conversation
@lexasq is attempting to deploy a commit to the Module Federation Team on Vercel. A member of the Team first needs to authorize it. |
Workflow status is failure ❌ |
Workflow status is failure ❌ |
const publicPath = `http://localhost:3001/` | ||
|
||
const doubleSlashRE = /\/\// | ||
const addPublicPath = url => (publicPath + url).replace(doubleSlashRE, '/') |
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.
Just asking shall we use global replace/replace all occurrences here?
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.
I believe it's autogenerated folder
Workflow status is failure ❌ |
@goldyfruit the readme has been changed, could you please try to check with the updated instructions? |
This is the error I got with the new README |
Hi, could you please share content of your env file? |
Workflow status is failure ❌ |
Workflow status is failure ❌ |
@goldyfruit I think I understood your struggle, the updates were made per app READMEs, duplicated those changes to common file as well, hopefully that'll help. |
Indeed, following the new README allows me to run The build instructions failed on Thanks for your help @lexasq |
Issues seems related to some files with port
|
@goldyfruit looks weird, just retested that and its fine. As for the build you got to check the respective instruction in the apps. |
@lexasq After changing port |
Don't change anything manually, follw the READMEs |
You most definitely didin't, |
But in this screenshot you are running on port |
When running |
One side note, maybe the main README should be updated with the correct ports as well: Thanks again for your help (and patience) @lexasq |
You can change port in the env file for prod, just don't forget to use the correct command for quasar, as for the dev you change port in the config file. |
Thanks! |
Workflow status is failure ❌ |
@@ -37,6 +37,8 @@ npm run format | |||
```bash | |||
yarn setup-env:prod | |||
quasar build | |||
cd dist spa |
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.
Should be dist/spa
.
@@ -37,6 +37,8 @@ npm run format | |||
```bash | |||
yarn setup-env:prod | |||
quasar build | |||
cd dist spa |
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.
Should be dist/spa
as well.
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.
Thanks, overlooked that!
Workflow status is failure ❌ |
Workflow status is failure ❌ |
Fix for #3173