Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

182
Views
Module federation, package versioning explanation

Despite my research online, I cannot find an explicit explanation of how package versions are resolved when I use webpack's Module Federation, so I'm hoping for some help.

Example 1: host (singleton version 16.x.x) client (singleton version 17.x.x) What Module Federation will use in this case? (I know that there will be some warnings in the dev tools, but I want a way to figure out what is actually being used)

Example 2: host (version 17.x.x) client (version 16.x.x) I think I figured this out based on semantic versioning, client will get version from host.

Is there any way to see what version webpack decides to use in the end and not rely in hypotheses?

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!