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

Problem creating web parts for ON-PREM 2019 #3752

Closed
Mhepplew opened this issue Apr 8, 2019 · 3 comments
Closed

Problem creating web parts for ON-PREM 2019 #3752

Mhepplew opened this issue Apr 8, 2019 · 3 comments
Labels
status:duplicate Duplicate of another issue. See comments for ref to other issue. Dupes closed to consolidate.

Comments

@Mhepplew
Copy link

Mhepplew commented Apr 8, 2019

I am trying to create SPFx web part FOR ON-PREM 2019 but facing issues on running the gulp serve command following creating a basic helloworld web part (no coding).

OS - Windows 10
Node version - 8.15.1
NPM version - 6.9.0
SPFx version - 1.8.0

I followed everything as per Microsoft documentation, which I have done successfully for ONLINE many times. However, when trying to create same but for ON-PREM 2019 the yoman generator doesn't create something that builds. gulp serve throws an error.

With some investigation I note that package.json dependancies are "~1.4.0" and devdependancies are "~1.4.1". The error complains about "@microsoft/sp-property-pane" which is in the header of the main web part (HelloWorldWebPart.ts).

With a little reading up, isn't "@microsoft/sp-property-pane" a SPFx 1.8.0 thing? Shouldn't the generator for ON-PREM 2019 be outputting 1.4 compatible code?

I build ONLINE web parts too so may well be that my environment is too 'latest/greatest' for On-PREM?

Can anyone provide the ideal node/npm/yo/SPFx etc. versions required to build ON-PREM 2019 SPFx web parts?

@msft-github-bot
Copy link
Collaborator

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

@msft-github-bot msft-github-bot added the Needs: Triage 🔍 Awaiting categorization and initial review. label Apr 8, 2019
@patmill
Copy link
Contributor

patmill commented Apr 8, 2019

See #3621 for more information and a workaround.

@patmill patmill closed this as completed Apr 8, 2019
@patmill patmill added status:duplicate Duplicate of another issue. See comments for ref to other issue. Dupes closed to consolidate. and removed Needs: Triage 🔍 Awaiting categorization and initial review. labels Apr 8, 2019
@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 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:duplicate Duplicate of another issue. See comments for ref to other issue. Dupes closed to consolidate.
Projects
None yet
Development

No branches or pull requests

3 participants