GithubHelp home page GithubHelp logo

module-federation / automatic-vendor-federation Goto Github PK

View Code? Open in Web Editor NEW
74.0 74.0 7.0 135 KB

Utility to enable automatic vendor sharing within bundles using Module Federation

License: MIT License

JavaScript 100.00%
federation module share vendor

automatic-vendor-federation's People

Contributors

chussum avatar dependabot[bot] avatar renovate[bot] avatar scriptedalchemy avatar semantic-release-bot avatar thekashey avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

automatic-vendor-federation's Issues

Support singleton config

How about support singleton config? React must be a singleton dependency, it'a a necessary config.

Watchpack Error (watcher): Error: EMFILE: too many open files, watch

I presume this is related to the max limit of open files by my OS (catalina 10.15.4). Looking for alternatives to changing this value, leaving that as a last resort.

For a specific repo with a lot of files, I've opted for the AutomaticVendorFederation. The build is now at + 28339 hidden modules. When webpack-dev-server launches, everything compiles successfully. After a few seconds my console is flooded with

Watchpack Error (watcher): Error: EMFILE: too many open files, watch

While ctrl+c will not kill the node process, I have to pkill node.

Am I meant to not watch these files or increase the limit?

Shared dependency package logic error

Consider below condition

  1. App1 project use package A, A depend on package B, but package B is not in App1 project package.json dependencies attribute.
  2. App2 project use package B in code and package.json dependencies have package B.

Result

package B is not shared, how to solved this condition

Other condition

without use AutomaticVendorFederation plugin, manual config shared package also have this case

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.