-
Notifications
You must be signed in to change notification settings - Fork 1k
Closed
Labels
area:spfxCategory: SharePoint Framework (not extensions related)Category: SharePoint Framework (not extensions related)status:fixed-next-dropIssue planned to be fixed in an upcoming release.Issue planned to be fixed in an upcoming release.type:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Description
Category
- Question
- Typo
- Bug
- Additional article idea
In SPFx v1.4 we have the ability to include assets in the package. If we were to include anything else than the main web part bundle (images, scripts that we'd like to dynamically load on runtime using SPComponentLoader), how would we refer to it in in code given that the URL is determined during deployment and the standard URL token (HTTPS://SPCLIENTSIDEASSETLIBRARY/
) is replaced only in the manifest but not in code?
luismanez, russgove, BigEaseGueldi, WhereCodeGoesToDie, andrewconnell and 1 more
Metadata
Metadata
Assignees
Labels
area:spfxCategory: SharePoint Framework (not extensions related)Category: SharePoint Framework (not extensions related)status:fixed-next-dropIssue planned to be fixed in an upcoming release.Issue planned to be fixed in an upcoming release.type:bug-suspectedSuspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.