You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
const{ js, css, ast }=svelte.compile(...);console.log(js.code);// stringconsole.log(js.map);// object with toString methodconsole.log(css.code);// stringconsole.log(css.map);// object with toString method
This can be done as a non-breaking change with a deprecation warning (until v2, when we'd switch over to the new API) by returning an object on which code, map and cssMap were getters that printed the warning, and by adding a toString method on css that also printed the warning.
The text was updated successfully, but these errors were encountered:
This is a relatively minor aesthetic thing, but the current API doesn't treat CSS as a first-class citizen. Rather than this...
...I think we should have this:
This can be done as a non-breaking change with a deprecation warning (until v2, when we'd switch over to the new API) by returning an object on which
code
,map
andcssMap
were getters that printed the warning, and by adding atoString
method oncss
that also printed the warning.The text was updated successfully, but these errors were encountered: