It would be great if we could have a new attribute for the <Page> element called import that lets us specify a module name to require/import, instead of it searching for a filename.
This will be very helpful in implementing a clean directory structure.
Also an extension on #1667; codeFile breaks in bundlers like webpack since bundles are by definition single-file. import fixes this by importing with global.loadModule.
@enchev, IIRC you were talking about turning CSS into modules for webpack and this could lend itself to that too by doing the same with a new stylesheet attribute -- with module.exports being a string.
It would be great if we could have a new attribute for the
<Page>element calledimportthat lets us specify a module name to require/import, instead of it searching for a filename.This will be very helpful in implementing a clean directory structure.
Also an extension on #1667; codeFile breaks in bundlers like webpack since bundles are by definition single-file.
importfixes this by importing withglobal.loadModule.@enchev, IIRC you were talking about turning CSS into modules for webpack and this could lend itself to that too by doing the same with a new
stylesheetattribute -- with module.exports being a string.