Skip to content

Conversation

ppossanzini
Copy link

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Docs
  • Underlying tools
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

Other information:

I have a group of microfronend applications, each one build as lib in a separate build process.
My CI/CD scripts place every build in a different server path, so i've change the publicPath in vue.config of each lib to match my publish path.
The main app load libs and use it correctly loading every lib at runtime via a json config from the correct subpath, but if a lib build has produced an additional chunk it fails if PRODUCTION env, because of publicPath has been resetted to '' and load of libs chunks happens from main app path and not from lib path; if i build in DEVELOPMENT mode it works, because in DEVELOPMENT env the cli does not reset the publicPath of lib .

Copy link

@suyundukov suyundukov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Linking the previous PR: #6257.

@ppossanzini you could simply change the target branch and rebase from dev, instead of creating a new PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants