A volo install was done for gaia-components/threads/master#threads.js. Since it was a single file install, it should have just installed threads.js. However, since the file name matched the name of the "main" module in the package.json, dependency scanning was done on it and since it has relative IDs mentioned in it (but not actually loaded since it is a built file of concatenated modules), the install wanted to keep a threads directory around.
However, the fragment ID request for the single file should override that other logic.
A volo install was done for
gaia-components/threads/master#threads.js. Since it was a single file install, it should have just installed threads.js. However, since the file name matched the name of the "main" module in the package.json, dependency scanning was done on it and since it has relative IDs mentioned in it (but not actually loaded since it is a built file of concatenated modules), the install wanted to keep athreadsdirectory around.However, the fragment ID request for the single file should override that other logic.