New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement: Page Imports #2986
Comments
Hi @vbresults thank you for your feature suggestion! Ping @hshristov , @enchev , @hdeshev |
@NickIliev Ok, let me know and I will submit a PR: https://github.com/vbresults/NativeScript/commit/b3427a48ebcdb728094e7200a658bfef56542913 |
I like the idea. It looks like we can deprecate the |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
It would be great if we could have a new attribute for the
<Page>
element calledimport
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 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
stylesheet
attribute -- with module.exports being a string.The text was updated successfully, but these errors were encountered: