Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

react-field-unique-permissions - error with build #1398

Open
1 of 9 tasks
spg-iwilson opened this issue Aug 11, 2024 · 2 comments
Open
1 of 9 tasks

react-field-unique-permissions - error with build #1398

spg-iwilson opened this issue Aug 11, 2024 · 2 comments
Labels
Needs: Triage 🔍 type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs

Comments

@spg-iwilson
Copy link

Sample

react-field-unique-permissions

Author(s)

@mkm17

What happened?

When I run the gulp --serve nobrowser command, the process fails after starting the tsc subtask. I've tried using Node 16.13.0 and 16.20.2

gulp serve --nobrowser

Debugger listening on ws://127.0.0.1:55123/7a8bd513-8732-4f02-94cc-60e397d3d40b
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Build target: DEBUG
[20:22:38] Using gulpfile ~\source\personal\Permissions-Field-Customizer\gulpfile.js
[20:22:38] Starting 'serve'...
[20:22:38] Starting gulp
[20:22:38] Starting subtask 'spfx-serve'...
[20:22:38] [spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/manifests.js
[20:22:38] Starting server...
[20:22:38] Finished subtask 'spfx-serve' after 336 ms
[20:22:38] Starting subtask 'pre-copy'...
[20:22:38] Finished subtask 'pre-copy' after 16 ms
[20:22:38] Starting subtask 'bump-revision-subtask'...
[20:22:38] gulplog v1 is deprecated. Please help your plugins update!
[20:22:38] Old Version: 1.0.0.61
[20:22:38] Old Build Number: 61
[20:22:38] New Build Number: 62
[20:22:38] New Version: 1.0.0.62
[20:22:39] Server started https://localhost:4321
[20:22:39] LiveReload started on port 35729
[20:22:39] Running server
[20:22:39] Finished subtask 'bump-revision-subtask' after 55 ms
[20:22:39] Starting subtask 'copy-static-assets'...
[20:22:39] Starting subtask 'sass'...
[20:22:40] Finished subtask 'sass' after 1.66 s
[20:22:40] Starting subtask 'tsc'...
[20:22:40] [tsc] typescript version: 4.5.5
[20:22:40] Error - [tsc] Debugger listening on ws://127.0.0.1:55308/186cb3c6-d731-4c25-a651-279409f63344
For help, see: https://nodejs.org/en/docs/inspector
[20:22:40] Error - [tsc] Debugger attached.
[20:22:41] Finished subtask 'copy-static-assets' after 2.22 s
[20:22:46] Error - [tsc] Waiting for the debugger to disconnect...
[20:22:46] Error - 'tsc' sub task errored after 6.15 s

Steps to reproduce

  1. NVM install 16.13.0
  2. NVM use 16.13.0
  3. Clone repository
  4. Run npm install
  5. Run gulp serve --nobrowser

Expected behavior

Gulp command should complete without errors

Target SharePoint environment

SharePoint Online

Developer environment

Windows

Browsers

  • Internet Explorer
  • Microsoft Edge
  • Google Chrome
  • FireFox
  • Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

Node.js version

v16.13.0

Additional environment details

No response

@spg-iwilson spg-iwilson added Needs: Triage 🔍 type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs labels Aug 11, 2024
@mkm17
Copy link
Contributor

mkm17 commented Aug 11, 2024

Hi @spg-iwilson,

I have double-checked the solution and I can successfully run the gulp serve --nobrowser command on the solution. When I compare the logs, the only suspicious line in your code is this one: Debugger listening on ws://127.0.0.1:55308/186cb3c6-d731-4c25-a651-279409f63344

Do you have the same issue with any other samples from the repository?

image

@spg-iwilson
Copy link
Author

Thanks @mkm17

I was able to build this on a separate machine. I didn't see the "Debugger listening" message on the that machine. I'm not sure why that message is displayed on the original machine.

I used the PnP SPfx VSCode extension to clone the react-field-unique-permissions project. I'll try cloning the whole repository and rebuilding on the original machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Triage 🔍 type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs
Projects
None yet
Development

No branches or pull requests

2 participants