-
Notifications
You must be signed in to change notification settings - Fork 1k
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
BUG: SPFx Builds Fail after March 19 ~1900UTC | gulp-core-build-typescript update breaks builds #501
Comments
Thanks @andrewconnell I've been trying to figure this issue out for the past few hours. |
Fixed with gcb-typescript 2.4.1. There is a shrinkwrap work item on the backlog as well. |
Not sure if it's related but I've just created a new project and while it's building, there are a few instances of the following warning displayed:
|
Little more detail for those tracking... here's the fix that @patmill referenced: microsoft/rushstack#140 Updated resolution step in my OP above to use the more current version... |
@waldekmastykarz check your TSLint... With the latest version & a clean project, I don't see any of that. |
@patmill since the 2.4.1 patch has been published for gulp-core-build-typescript, appears this issue is now moot. This should be flagged as a bug... but I'm going to go ahead and close it. |
I've just created a brand new project @andrewconnell (no JS framework): still the same error |
Error is reported only on a vanilla SPFx project. After scaffolding the project and running
no error is reported anymore. |
Hey Waldek - for the one that doesn't work, what version of gcb-typescript is getting used? Could the wrong version be cached in your machine?
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Waldek Mastykarz <[email protected]>
Sent: Monday, March 20, 2017 6:52:32 AM
To: SharePoint/sp-dev-docs
Cc: Pat Miller (SHAREPOINT); Mention
Subject: Re: [SharePoint/sp-dev-docs] BUG: SPFx Builds Fail after March 19 ~1900UTC | gulp-core-build-typescript update breaks builds (#501)
Error is reported only on a vanilla SPFx project. After scaffolding the project and running
npm i @microsoft/gulp-core-build-typescript -D
no error is reported anymore.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#501 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADl-SbSacjiqmyQ7GnVMDoWocZBKcdRMks5rnoSggaJpZM4Mh9ry>.
|
It's on @microsoft/[email protected] @patmill |
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 |
Category
Expected or Desired Behavior
Builds succeed on the default project created from accepting all defaults in the Yeoman generator.
Observed Behavior
Builds fail TypeScript transpilation step... specifically the subtask typescript. Errors start with the following & yield 25 errors.
Steps to Reproduce
$ yo @microsoft/sharepoint
and accept all defaultsSteps to Resolve
Uninstall the updated gulp-core-build-typescript package updated March 19, 2017 ~1900 UTC (see microsoft/rushstack@0a793bc for commit that triggered the issue) which is version 2.4.0.
Revert back to 2.3.0 which will work.Install 2.4.1 which patches the issue that caused this regression (see below for info).gulp build
and the project will successfully transpile.PERSONAL REQUEST by OP
Microsoft SPFx Engineer: PLEASE PLEASE consider this a feature request... PLEASE shrink wrapping ref npm shrinkwrap the dev tools... this is the second time an upstream dependency has broken development for your adopters of the SharePoint Framework and it's unecessarily giving SPFx a bad rep. I thought the #394 "lodash-gate" incident would have been enough to consider this prior to GA. This is a common technique for packages that have significant number of dependencies such as this.
The text was updated successfully, but these errors were encountered: