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
Hi. Thanks for this, I was writing a loader to do this and researching when I discovered it.
One thing I would like would be an option to pass a block to loaders defined in config. Vue-Loader was recently updated to work that way, but I haven't looked at how they do it. Maybe by enabling a "useConfig" option, the loader could add each block as a dependency or figure out a way to load the one file as other types with an inline option to only load a certain block (or filter out other). The type specified like <style lang="sass">. I'm wondering how difficult it would be to implement something like this so people could easily use existing configs and the same config used for .one files would be used for import statements in files.
I'm sure this could be done from config side by storing each config in a var, too, just wondering if it could be integrated. Thanks.
The text was updated successfully, but these errors were encountered:
Hi. Thanks for this, I was writing a loader to do this and researching when I discovered it.
One thing I would like would be an option to pass a block to loaders defined in config. Vue-Loader was recently updated to work that way, but I haven't looked at how they do it. Maybe by enabling a "useConfig" option, the loader could add each block as a dependency or figure out a way to load the one file as other types with an inline option to only load a certain block (or filter out other). The type specified like
<style lang="sass">
. I'm wondering how difficult it would be to implement something like this so people could easily use existing configs and the same config used for.one
files would be used forimport
statements in files.I'm sure this could be done from config side by storing each config in a var, too, just wondering if it could be integrated. Thanks.
The text was updated successfully, but these errors were encountered: