0

I recently upgraded our webpart project from SPFX 1.12 to 1.19 Node to Version 18 and Gulp to version 5. I know - big changes. The build is fine no errors or issues but no files are created.
Because this upgrade included the tsLint depreciation I did remove the tsLint file but other than that no major changes except to PNPJS for the upgrade to PNPJS 4.0.

After doing a Build --ship and/or Bundle --ship (which are both successful even with debugging) I run the gulp package --ship and get the error no manifest files can be found at manifest/release. The files used to be stored at sharepoint/solution and I note that a gulp clean doesn't clear that folder anymore. If I manually create a manifest/release folder gulp clean will remove it, but gulp build --ship still won't populate it.

I do have a zippedPackage: solution/solution name defined in my package-solution.json I tried updating that to manifest/release/solution name and release/solution name but nothing works. Also noted when I launch Gulp Serve although the Gulp Server is running it tells me it can't launch the webparts to ensure the server is running so pretty sure it's not creating the files to do this either. Any ideas?

Improve this question
5
  • Nothing suspicious if build or served or packaged via --verbose argument? Commented Sep 16, 2024 at 8:10
  • Well I rebuilt the whole project using a fresh SP19 regenerated Webpart to see if that did anything and now the release folder is getting created but when I run verbose I just get Webpack dist Error [Object][Object]. My lib folder is created correctly but my manifest file entries are blank. The names are listed but no values. Commented Sep 20, 2024 at 19:02
  • I've tried all the suggestions around the [object][object] error I have found with varying versions of react and pnp property controls to no avail. Commented Sep 20, 2024 at 19:03
  • I added the mgt-spfx dependency and now I have a package file. However SOME of the webparts in the package are throwing the Error [Object][Object] in Gulp Serve or after being deployed and used. The only error in the console is Cannot read Properies of undefined (reading 'id') Commented Sep 20, 2024 at 20:10
  • This GitHub thread you may find helpful--> github.com/SharePoint/sp-dev-docs/issues/9675 Commented Sep 21, 2024 at 19:07

1 Answer 1

Reset to default
0

I faced somewhat similar issue. You can check it here Link

For me this [object object] issue occurred due to 2 reasons.

  1. SPFX v1.19.0 supports React v17.0.1.
  2. Unwanted localizedResources mentioned in config.json.
Improve this answer
1
  • I am using React 17.0.1. I'll look into localizedResources mentioned in config.json you mentioned I haven't seen any errors nothing pops up during build or gulp serve except that Object Object... Commented Sep 22, 2024 at 22:32

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.