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

NPM Errors #1227

Closed
1 of 9 tasks
chasquad opened this issue Feb 28, 2024 · 3 comments · Fixed by #1229
Closed
1 of 9 tasks

NPM Errors #1227

chasquad opened this issue Feb 28, 2024 · 3 comments · Fixed by #1229
Labels
Needs: Triage 🔍 type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs

Comments

@chasquad
Copy link

chasquad commented Feb 28, 2024

Sample

React-Application-Announcements

Author(s)

@martincyr @mikemyers

What happened?

Cloned the repository. Then I did npm install. This is where I got these errors.

Steps to reproduce

  1. Cloned Repository
  2. Navigated to my cloned repository location
  3. Used PowerShell did command npm install

Expected behavior

Expected no errors.
2024-02-28T21_21_02_217Z-debug-0.log

Target SharePoint environment

SharePoint Online

Developer environment

None

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

v18.19.0

Additional environment details

No response

@chasquad chasquad added Needs: Triage 🔍 type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs labels Feb 28, 2024
@ghost
Copy link

ghost commented Feb 28, 2024

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@chasquad
Copy link
Author

@martincyr
@thespooler

I may not have done the @ mentions correctly when I submitted the issue. Sorry .. I'm new!

@thespooler
Copy link
Contributor

This sample was written in the SPFx 1.10 days, so it requires NodeJS version 8 or 10. You were building it using Node 18, and for SPFx, node and npm versions matters.
I will be submitting a PR to get it running with more recent version of SPFx.

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

Successfully merging a pull request may close this issue.

2 participants