UNPKG

create-mashup-app/CHANGELOG.md

Version:

1.29 kBMarkdownView Raw

1# v.2.0.0
2
3- rewritten from scratch to use rollup instead of webpack
4- add mashup rollup plugin that handles code splitting, injects minimalistic chunk loader, and manages TP dependency sharing between separate chunks
5- typescript now works out of the box
6- use cosmiconfig for mashup configuration instead of relying on `mashup.json` file being present
7
8### Breaking changes:
9
10- configuration is now handled by cosmiconfig; as such, `mashup.json` is no longer valid config file name.
11- rollup is now used internally, so your existing webpack config transform won't work.
12
13### Migration guide:
14
15- rename your `mashup.json` to `.mashuprc` or `.mashuprc.json`, or inline it under `"mashup"` key in your `package.json`.
16- if you have any custom transform function, they will most likely not work, because they assume webpack configuration. 2.0 is written in rollup, so you'll need to update your custom transform. Ideally, the issue you were trying to fix with this transform is no longer present, and you don't need it at all.
17- make sure both build and dev server work for you and produce correct output.
18- if you use code splitting, verify that all chunks are handled correctly; you'll need to provde `--baseUrl` when using `build` to specify where your chunks reside.

1	`# v.2.0.0`
2
3	`- rewritten from scratch to use rollup instead of webpack`
4	`- add mashup rollup plugin that handles code splitting, injects minimalistic chunk loader, and manages TP dependency sharing between separate chunks`
5	`- typescript now works out of the box`
6	- use cosmiconfig for mashup configuration instead of relying on `mashup.json` file being present
7
8	`### Breaking changes:`
9
10	- configuration is now handled by cosmiconfig; as such, `mashup.json` is no longer valid config file name.
11	`- rollup is now used internally, so your existing webpack config transform won't work.`
12
13	`### Migration guide:`
14
15	- rename your `mashup.json` to `.mashuprc` or `.mashuprc.json`, or inline it under `"mashup"` key in your `package.json`.
16	`- if you have any custom transform function, they will most likely not work, because they assume webpack configuration. 2.0 is written in rollup, so you'll need to update your custom transform. Ideally, the issue you were trying to fix with this transform is no longer present, and you don't need it at all.`
17	`- make sure both build and dev server work for you and produce correct output.`
18	- if you use code splitting, verify that all chunks are handled correctly; you'll need to provde `--baseUrl` when using `build` to specify where your chunks reside.