Replies: 2 comments
-
Was digging through the source code to see if I could shim it in, and found the Unit test I was looking for. The mount option in the snowpack.config.js file contains the necessary feature to push in a module directory which can then later be loaded manually using the dynamic import() The problem with this approach is that the main system will not consider these files as part of the packaged files. So the imports of those files will not be changed... |
Beta Was this translation helpful? Give feedback.
-
Ended up scrapping this approach. Started looking into using references for tsconfig.json and came up with a small feature change at #3801 |
Beta Was this translation helpful? Give feedback.
-
I have a bit of a weird request I am trying to figure out. So Snowpack likes to have references to a resource in order for it to actually import that npm resource to the project _snowpack folder, however what I am wanting to do is have files from a module included into the
_snowpack
folder for later loading dynamically through an async request. This is primarily done as sometimes scripts are disabled from being used.Any ideas of how to do this with snowpack? I was looking at the
import.meta.globEager("/BootstrapBind/*");
approach, but while that allows the project to work, it makes the imports mandatory which is not entirely ideal.If I could specify a directory and say, "make sure to include this to the destination" that would be the ideal approach.
To be clear, this is a library (we have) I am referencing, not my own project files.
Beta Was this translation helpful? Give feedback.
All reactions