The first line we’re already familiar with (SPLoaderError.loadComponentError), so now we’ll take a look at 2 different interesting things.įirst of all, we can identify the faulting components by investigating the component IDs – probably, the most interesting line is the INNERERROR: You’ll be interested in a couple of things here. ***Failed to load path dependency "ContosoSPFxWebPartLocalization" from component "9951b316-c8f2-4e27-887a-b7a46b3e94a0" (ContosoSPFxWebPart).Īt Function.e.buildErrorWithVerboseLog () Original error: ***Failed to load path dependency "ContosoSPFxWebPartLocalization" from component "9951b316-c8f2-4e27-887a-b7a46b3e94a0" (ContosoSPFxWebPart). Sometimes you have the sick-looking “…” -url, sometimes you see an absolute url – let’s take a closer look at the stack below! : ![]() I’ve seen a few different variations out of this error. Now all that’s left is figuring out what the reason is! So looking at this, what’re the actual errors we’re getting? Where are they stemming from?įrom the first line (“ SPLoaderError.loadComponentError“) we already know that it’s about the SPFx failing to load your component for whatever reason. But first, let’s take a closer look into the error in question! I’m trying to describe the variants I’ve run into and their fixes below. This error can be thrown for a lot of different reasons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |