SharePoint Framework debugging issue

Copper Contributor

Hi 

 

Did anyone face the following issue

While I was debugging SP Framework code I got "Unverified break point" at any break point. I followed all steps but still got same issue. I saw following error in debug console.

 

Failed to load resource: the server responded with a status of 404 (Not Found) [https://localhost:4321/temp/workbench-packages/@microsoft_sp-loader/dist/sp-loader-assembly_default.js]
 
Failed to load resource: the server responded with a status of 404 (Not Found) [https://localhost:4321/temp/workbench-packages/@microsoft_sp-webpart-workbench/lib/api/workbenchInit.js]
 
Failed to load resource: the server responded with a status of 404 (Not Found) [https://localhost:4321/temp/workbench-packages/@microsoft_sp-loader/dist/sp-loader-assembly_default.js]
 
Refused to execute script from 'https://localhost:4321/temp/workbench-packages/@microsoft_sp-loader/dist/sp-loader-assembly_default.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. [https://localhost:4321/temp/workbench.html]
 
Failed to load resource: the server responded with a status of 404 (Not Found) [https://localhost:4321/temp/workbench-packages/@microsoft_sp-webpart-workbench/lib/api/workbenchInit.js]
 
Refused to execute script from 'https://localhost:4321/temp/workbench-packages/@microsoft_sp-webpart-workbench/lib/api/workbenchInit.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. [https://localhost:4321/temp/workbench.html]
 
TypeError: Cannot read property 'start' of undefined
workbench.html:69
at c:\spfxdemo\temp\workbench.html:69:30
 
 
3 Replies

I am facing exactly same issue. Were you able to figure it out?

No I have no resolution. I am waiting for a reply here with resolution.

If you find something please post it here. I will do same.

 

Thanks.

 

 

https://github.com/SharePoint/sp-dev-docs/issues/2507

I was facing the same problem recently. I found the suggestion in the above github issue helpful to solve this exact problem. As noted in the issue, this only occurs for projects using spfx 1.5 and up. You will have to launch https://localhost:5432/workbench

instead of https://localhost:4321/temp/workbench.html