Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Improve the default text output when upgrading an SPFx project

See original GitHub issue

It might just be me, but when updating an SPFx solution using the CLI, I always output the report as an md file, and I always scroll to the summary to get the aggregated pieces of what I need to do.

So for me, having a default ouput as a file named something like upgrade-1.4.0-1.5.1.md, and also having the summary at the top and not at the bottom of the report would save me a few keystrokes and seconds 😃

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:8 (4 by maintainers)

Top GitHub Comments

2reactions

wobbacommented, Sep 22, 2018

Works for me and a good solution.

2reactions

wobbacommented, Sep 13, 2018

This is how I’d like to see the text output.

Console command
---------------------
npm i @microsoft/sp-core-library@1.6.0 --save-exact
npm i @microsoft/sp-lodash-subset@1.6.0 --save-exact
npm i @microsoft/sp-office-ui-fabric-core@1.6.0 --save-exact
npm i @microsoft/sp-webpart-base@1.6.0 --save-exact
npm i @microsoft/sp-dialog@1.6.0 --save-exact
npm i @microsoft/sp-application-base@1.6.0 --save-exact
npm i @microsoft/decorators@1.6.0 --save-exact
npm i @microsoft/sp-build-web@1.6.0 --save-exact -D
npm i @microsoft/sp-module-interfaces@1.6.0 --save-exact -D
npm i @microsoft/sp-webpart-workbench@1.6.0 --save-exact -D
npm i tslint-microsoft-contrib@5.0.0 --save-exact -D

.yo-rc-json
------------
{
  "@microsoft/generator-sharepoint": {
    "version": "1.6.0"
  }
}

etc.