VueDart 0.3.1 released!
Aspen and aspen_assets 0.2
VueDart 0.3.1's CLI (CLI version 0.1.1) brings in version 0.2 of aspen_assets . Although aspen_assets itself does not have many changes, it is simply a way of accessing the much-improved Aspen asset packer , with an improved CLI interface and automated global asset loading.
Scoped styles no longer bleed
This is technically a breaking change; however, as far as I know, no projects depended on the old behavior.
In VueDart 0.3, scoped styles would "bleed" by default into children, in order to support the styling of v-html elements and other similar items (e.g. jQuery plugins):
<template vuedart>
<div v-html="'<p>This is inside v-html!</p>'">
</template>
<style scoped>
p {
background-color: purple;
}
<style>
However, there was a bug where these styles would also go into any child components, which basically defeated the entire purpose of scoped styles. Now, by default absolutely no bleeding will take place. If you want bleeding, you can use the bleeds attribute:
<template vuedart>
<div v-html="'<p>This is inside v-html!</p>'">
</template>
<style scoped bleeds>
p {
background-color: purple;
}
<style>
Note that now, even if you pass bleeds , styles will only bleed into everything except VueDart components. This behavior is less error-prone than before.
The majority of these changes are thanks to scopify 0.2 .
Minor documentation tweaks
The documentation now better explains the significance of the entry_points argument to the VueDart transformer.