Releases: l7aromeo/meonode
Release list
@meonode/compiler@0.7.0
Minor Changes
-
#4
151fdf5Thanks @l7aromeo! - Rewritetheme.*tokens insidecssblocks at build time.The token rewrite previously stopped at the top level of a props object, so
every token in acss:block was still converted on each render. It now
recurses intocssobject literals, choosing the plain or--lenvariable form
from the nearest enclosing property — with selectors and at-rules (&:hover,
@media …) contributing none, matching@meonode/ui's own rule.Keys are still never rewritten:
var()is invalid inside media features and
selector text, so a token in a key must resolve against the live theme at
runtime. Arrays and tokens in non-selector keys are skipped for the same
reason — the property name they resolve to is not knowable at build time.Beyond skipping the string replacement, a
cssblock whose keys hold no tokens
now scans clean inThemeUtil.resolveObjWithTheme, so its whole copy-on-write
walk collapses to returning the input unchanged.
@meonode/ui@1.8.7
Patch Changes
- #1
5d234acThanks @l7aromeo! - Point the package metadata at the new monorepo.repository,bugsandhomepagereferenced the three separate repositories that have now been merged into l7aromeo/meonode, and each package gains arepository.directoryso npm links to its own subtree. No functional change — npm reads these fields from the published tarball, so a release is the only way to correct them.
@meonode/mui@1.5.11
Patch Changes
- #1
5d234acThanks @l7aromeo! - Point the package metadata at the new monorepo.repository,bugsandhomepagereferenced the three separate repositories that have now been merged into l7aromeo/meonode, and each package gains arepository.directoryso npm links to its own subtree. No functional change — npm reads these fields from the published tarball, so a release is the only way to correct them.
@meonode/compiler@0.6.2
Patch Changes
- #1
5d234acThanks @l7aromeo! - Point the package metadata at the new monorepo.repository,bugsandhomepagereferenced the three separate repositories that have now been merged into l7aromeo/meonode, and each package gains arepository.directoryso npm links to its own subtree. No functional change — npm reads these fields from the published tarball, so a release is the only way to correct them.