gulp issue - gulp error with current cfailing to generate manifest.js #5360
Labels
type:bug-suspected
Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs
Disclaimer
Yes
Sample
react-group-teams
Contributor(s)
Alison Collins
What happened?
Couple of issues - first one - latest gulp version gives an error message (ReferenceError: primordials is not defined) - was able to partially resolve this by workarounds involving preinstall scripting and updating graceful-fs dependencies.
However after getting the package to seemingly complete the build process (it didn't actually), while 'gulp serve --nobrowser' did start a server, it failed to produce a manifest file. The only temp packages downloaded were relating to the (now obsolete?) workbench. Have successfully built other V14 packages - this one has issues the others don't. I assume it works fine within the Docker environment (assume it does), however due to security restrictions I can no longer use Docker at my workplace and need to build locally. Tried to activate the package in my developer tenant however 'something went wrong' and the error only reported '[object Object]'.
gulp serve errors.txt
Steps to reproduce
Follow minimal path to awesome.
3.Gulp Local 3.9,1
Expected behavior
manifest file to be created by gulp serve --nobrowser so web part can be tested using &debugManifestsFile=https://localhost:4321/temp/manifests.js
Target SharePoint environment
SharePoint Online
Developer environment
Windows
Browsers
What version of Node.js is currently installed on your workstation?
14.21.3
What version of Node.js is required by the sample?
v14
Paste the results of SPFx doctor
installed m365-cli, can't even log into it - getting an error 'cannot find package 'timers' - googled this error - m365 apparently does not work with node v14 .. which is the version this spfx webpart is made for.
Additional environment details
No response
The text was updated successfully, but these errors were encountered: