Releases: adambullmer/vue-cli-plugin-browser-extension
Releases · adambullmer/vue-cli-plugin-browser-extension
0.21.1
0.21.0
Upgrading to this version does not require that you run vue invoke browser-extension
. The changes only affect how a freshly scaffolded project will look for its files.
- Added typescript scaffolding support
- Restructured the pages to be more in line with general vue practices, like
main.js
instead of a custom name - Optimized some dependency trees to avoid putting more things into the parent project
- Removed additions of vuex and vue-router for now
0.20.0
Ramping up for a stable release
Breaking changes
- added new option for the artifact directory,
artifactDir
, changed default zip output directory from{{webpack.output}}-zip
toartifacts
Dangerous
- Re-enabled the node global.
webpackConfig.node.global = true
. I don't recall why it was off in the first place, and being off is causing some issues later outlined in #12.
Scaffolding Changes
- Renamed the scaffolded pages to no longer need a namespace
popup/popup
becamepopup
- cleaned up name on
content-scripts
folder - converted most of the webpack configurations into the community preferred webpack chain
- added back codesplitting optimizations for pages with html files (ignores background and content-scripts)
- added back production filename hashing
popup.abcd1234.js
on pages with html files (ignores background and content-scripts)
These scaffolding changes help remove a sticking point for resolving CSS assets with the absolute project root ~@/
syntax
0.19.0
Added signing key generation option to scaffold
0.18.1
- Fixed ExtensionReloader production warning.
- Refactored the manifest transform to be more performant.
0.18.0
Added devtool scaffolding
0.17.1
fixed manifest.json scaffolding bug
0.17.0
v0.17.0
0.16.0
- Include generic browser reload package instead of chrome specific package
- Bump risky outdated packages
0.15.1
v0.15.1