SharePoint FrameWork ERROR_CONNECTION_REFUSED accessing Manifest.js

Question

My Spfx solutions suddenly stop working even after multiple updates not reflecting the changes I made.

Answer 1

Hi @MERSAN CANONIGO JR ,

If you're encountering an when accessing in your SharePoint Framework (SPFx) solutions, Here are some steps you can take to troubleshoot the issue:

1. Check Local Server: Ensure that your local development server is running. You can start it by navigating to your project folder and executing in the command line.gulp serve --nobrowser
2. Correct URL Parameters: Make sure you are appending the correct parameters to the URL of the SharePoint page where you are testing your SPFx web parts.
3. Browser Compatibility: Sometimes, certain browsers may have issues with local development. Try using a different browser or check the browser's console for any additional error messages.
4. Update Packages: If you haven't already, ensure that your Yeoman template packages are updated. You can do this by deleting the folder and running again.node_modulesnpm install
5. Update Node.js and npm: Ensure that you have the latest versions of Node.js and npm installed. Sometimes, outdated versions can cause issues with loading dependencies.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi @MERSAN CANONIGO JR ,

I'm glad to hear you solve the problem, I would make a brief summary of this thread:

Issue Symptom:

SharePoint FrameWork ERROR_CONNECTION_REFUSED accessing Manifest.js

Current status:

The issue has been solved. Solved this issue using this:

gulp clean

gulp test

gulp serve --nobrowser

then attach loadSPFX=true &debugManifestsFile=https://localhost:4321/temp/manifests.js in the workbench URL

then upon deployment:

gulp clean

gulp test

gulp build

gulp bundle --ship

gulp package-solution --production

You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!