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
So, I've manipulated this so that I have extended the manifest loadOrder with my own, and I have files on the metadata. But obviously when it goes to load the urls, it fails....
The text was updated successfully, but these errors were encountered:
The below snippet outlines the loadScripts function.
package-loader/packages/package-loader/src/package/Entry.js
Lines 60 to 78 in 49c0699
When it runs through the files, it will look them up in the loadOrder and then append them to a paths array:
package-loader/packages/package-loader/src/package/Entry.js
Lines 70 to 73 in 49c0699
However, it appears that the load function doesn't handle urls being an array, yet clearly the loadScripts is expecting at some point to pass it one.
package-loader/packages/package-loader/src/package/Entry.js
Lines 80 to 102 in 49c0699
So, I've manipulated this so that I have extended the manifest loadOrder with my own, and I have files on the metadata. But obviously when it goes to load the urls, it fails....
The text was updated successfully, but these errors were encountered: