|
1 | 1 |
|
2 | 2 |
|
| 3 | +## [8.0.0](https://github.com/Patternslib/patterns/compare/7.12.0...8.0.0) (2022-05-17) |
| 4 | + |
| 5 | + |
| 6 | +### Features |
| 7 | + |
| 8 | + |
| 9 | +* **Build:** Dynamic Module Federation. Add config files and helpers. ([7e7a2af](https://github.com/Patternslib/patterns/commit/7e7a2afea57caa6d97dc045e77e001e64c676ab2)) |
| 10 | +With module federation you can share dependencies over multiple bundles without |
| 11 | +loading them multiple times. |
| 12 | + |
| 13 | +The dynamic part here allows the host to not know anything about it's remotes. |
| 14 | +This concept can be used for add-ons to a base bundle. |
| 15 | +Thanks @manfredsteyer for the help getting this to work! |
| 16 | + |
| 17 | +Use the webpack/webpack.mf.js to extend your own webpack configuration with |
| 18 | +dynamic module federation support. |
| 19 | +In your main bundle (the "host") use webpack/dynamic_mf.js to configure the |
| 20 | +entry point. |
| 21 | + |
| 22 | +For more information see: docs/developer/module-federation.md. |
| 23 | +For the general concept see: https://webpack.js.org/concepts/module-federation/ |
| 24 | + |
| 25 | +Co-authored-by: Johannes Raggam <thetetet@gmail.com> |
| 26 | +Co-authored-by: Manfred Steyer <manfred.steyer@gmx.net> |
| 27 | + |
| 28 | +* **Build:** Register jQuery globally without expose-loader. ([dca0842](https://github.com/Patternslib/patterns/commit/dca08426108a0180500210e9625c8abfc5294fd2)) |
| 29 | +Remove the dependency on expose-loader and register jQuery globally in the |
| 30 | +globals.js module. |
| 31 | + |
| 32 | +Import this module early to have jQuery registered for scripts which depend on |
| 33 | +a global jQuery object. |
| 34 | + |
| 35 | +This also fixes an additional request made by the expose-loader for |
| 36 | +asynchronously loading jQuery. |
| 37 | + |
| 38 | +* **core dom:** dom.template engine. ([61ca46f](https://github.com/Patternslib/patterns/commit/61ca46fac5b34a69814617dffe89665fd3506095)) |
| 39 | +Add a simple template engine in ``core.dom.template`` |
| 40 | +based on JavaScript template literals. |
| 41 | + |
| 42 | + |
| 43 | +### Maintenance |
| 44 | + |
| 45 | + |
| 46 | +* **Build:** Compatibility with Jest 28. ([1795087](https://github.com/Patternslib/patterns/commit/17950874de41ac053b26a5d629434e829a0d74e8)) |
| 47 | +Don't transform preact. |
| 48 | + |
| 49 | +* **Build:** Compatibility with Jest 28. ([69b7934](https://github.com/Patternslib/patterns/commit/69b793416f99a7097c91f5f58aeba49495c3c1ea)) |
| 50 | +Remove jest-raw-loader dependency and add own loader based on https://github.com/keplersj/jest-raw-loader/pull/239/ for compatibility with Jest 28. |
| 51 | + |
| 52 | +* **Build:** Compatibility with Jest 28. ([5679db0](https://github.com/Patternslib/patterns/commit/5679db0d84eda485737647cac480cc808badd194)) |
| 53 | +Add jest-environment-jsdom as of jest 28 that isn't shipped anymore by default. |
| 54 | + |
| 55 | +* **Build:** Upgrade dependencies. ([3260038](https://github.com/Patternslib/patterns/commit/3260038cf2772de50065df20eceec7473625b050)) |
| 56 | + |
| 57 | + |
| 58 | +* **Build:** Upgrade fullcalender. ([0b08573](https://github.com/Patternslib/patterns/commit/0b08573b67e65bb6d300c2810d8abe8173954e73)) |
| 59 | + |
| 60 | + |
| 61 | +* **Build:** Upgrade luxon to version 2. ([5d12b9e](https://github.com/Patternslib/patterns/commit/5d12b9ec47344efc0dcc8e8126d1d4db3a6e3c6d)) |
| 62 | + |
| 63 | + |
| 64 | +* **Bundle:** Upgrade jest to version 28. ([4ac079f](https://github.com/Patternslib/patterns/commit/4ac079f184043225ff78aded9390ae9f995036d0)) |
| 65 | + |
| 66 | + |
| 67 | + |
| 68 | +### Breaking Changes |
| 69 | + |
| 70 | + |
| 71 | +* **core registry:** Use a global pattern registry. ([737f3ed](https://github.com/Patternslib/patterns/commit/737f3ed0577550483fa552cf995e39076429bc3b)) |
| 72 | +Previously it was possible to use multiple pattern registries when multiple |
| 73 | +instances of the registry were used, e.g. in different bundles. |
| 74 | + |
| 75 | +With this change we do use only one pattern registry storage which is |
| 76 | +shared across instances of ``core.registry`` in multiple bundles. |
| 77 | + |
| 78 | +This is a transparent change - the Patternslib registry API has not |
| 79 | +changed at all. Just keep using ``registry.scan``, |
| 80 | +``registry.register``, etc. |
| 81 | + |
| 82 | +But if necessary, there is a ``PATTERN_REGISTRY`` export in ``core.registry`` |
| 83 | +which points to ``window.__patternslib_registry``, a singleton in the global |
| 84 | +namespace which is shared across instances of the registry. |
| 85 | + |
3 | 86 | ## [7.12.0](https://github.com/Patternslib/patterns/compare/7.11.0...7.12.0) (2022-05-13)
|
4 | 87 |
|
5 | 88 |
|
|
0 commit comments