Skip to content

Latest Node.js LTS version (8.9.0) doesn't work in SharePoint Framework web part development #1013

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

Closed
ollij opened this issue Nov 2, 2017 · 7 comments

Comments

@ollij
Copy link

ollij commented Nov 2, 2017

Updating to the latest Node.js LTS version 8.9.0 causes security error when creating new web part project and doing gulp serve.

Category

  • Bug

Expected or Desired Behavior

After gulp serve command browser opens and workbench loads correctly.

Observed Behavior

Edge: Can’t connect securely to this page - This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.
Chrome: This site can’t provide a secure connection - localhost sent an invalid response. - ERR_SSL_PROTOCOL_ERROR

Steps to Reproduce

  1. Uninstall current version of Node.Js
  2. Install latest LTS version (8.9.0) of Node.js from https://nodejs.org/en/
  3. Create new web part project with Yeoman using the default values
  4. Execute gulp serve
@kimpihlstrom
Copy link

This behavior is also reproducible on all major browsers (Chrome, Firefox, IE, Egde, etc).

Possible workaround is to uninstall the current LTS relase of NodeJS and download the previous LTS release, https://nodejs.org/download/release/v6.11.5/.

@waldekmastykarz
Copy link
Collaborator

Could it be the same as #1002?

@yogsodoth
Copy link

I had this issue, followed procedure for #1002 and it now works.

@adambu
Copy link
Contributor

adambu commented Nov 3, 2017

+1 from my customer. Created a pull request for https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment

@patrick-blanc
Copy link

Thanks @waldekmastykarz, it works fine. See #1002

@qz2017
Copy link

qz2017 commented Jan 9, 2018

Closing this ticket as dupe of 1002

@qz2017 qz2017 closed this as completed Jan 9, 2018
@msft-github-bot
Copy link
Collaborator

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues

@SharePoint SharePoint locked as resolved and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants