Discussion on "Package SPFx solution with one command and automatically increase the version"

$€®¥09@ · 2022-06-17T10:15:06.139Z

Optimize SPFx packaging with auto-version increment in one command for seamless updates, syncing package-solution.json and package.json

Discussion on "Package SPFx solution with one command and automatically increase the version" | Hashnode

Responses4

Markdown supported · ⌘↵ to post

Jonathan Adcox

Jun 24, 2024

Very useful. Deployed it instantly

Jonathan Adcox

Jun 28, 2024

$€®¥09@ to the Gulp command in the article. However there were a few bugs. When I build and clean it will not run as intended and only when I use the gulp command directly does it build properly and it builds with Major version only. Did you address this in the comments?

$€®¥09@

Jonathan Adcox Hmmm, where exactly is the error? I've never had this before. I use npm run publish and this command does a gulp clean and then a gulp build, gulp bundle --ship, gulp bump-version and then gulp package-solution --ship one after the other.

Normally only the patch version is updated, unless you specify something else.

By the way: If you use the command npm run publish and there was a warning/error in the console output, then the commands are not executed, with the output exit with code 1 (or something like that). This is due to the && command combination. But you can prevent this by disabling the warnings.

PS: As mentioned in the other comments, I can recommend using my CLI, which does exactly the same settings as described in this article, and does so with a command line and also adds the "disable warnings" command. And some more. Here is the link to the CLI article (with Video): spfx-app.dev/my-cli-for-spfx-development

Jonathan Adcox

Jun 28, 2024

$€®¥09@ oh I already disabled those errors due to an unused variable that is only accessed in SharePoint however in the build it is never used. As such I had to disable the warning to build the solution. I likely fat fingered something. I will go back and see what I transposed wrong

$€®¥09@

Dec 9, 2022

Hello Thomas Leclaire, hello Sujit Daswant,

now you can use my newly released npm package @spfxappdev/cli. This package is a command-line utility that modifies your SharePoint Framework solution so that you can use the versioning logic described above without additional modifications. You can use "alias" paths instead of relative paths. Also, an automatic "version increment" task (gulp) is included and you can build, version, bundle and package the solution with just one npm command.

A blog post will follow in the next few days.

Sujit Daswant

Sep 16, 2022

Hi Sergej Schwabauer, I am really appreciate for this blog, this is helped me lot for Auto increment the the version number.

But I am facing issue with the above, when I am trying to run the command for npm run publish -- --no-patch,npm run publish -- --major,npm run publish -- --minor version always the minor version get updated even for no patch also.

Please let me know how to fix this.

Thomas Leclaire

Jun 17, 2022

How would you use this in an Azure Devops Deployment pipeline where you would have to save the increased version back to the repo?

Thomas Leclaire Thank you for your comment. Please have a look at this newly created post. I hope it helps you: spfx-app.dev/spfx-azure-devops-pipeline-increment…

$€®¥09@

Sep 19, 2022

Sujit Daswant Okay, I understand. And now I know what you mean and what the problem is. The npm run command with the additional arguments is only added to the "last" command (in our case ==> gulp package solution command). But we need this argument in the gulp bundle command. Thanks for your hint. To fix it, you need to create a post-script and modify the "publish" script:

"publish": "gulp clean && gulp build && gulp bundle --ship",
"postpublish": "gulp package-solution --ship"

Thanks again and I have already changed it in the post above.

Search Hashnode

Package SPFx solution with one command and automatically increase the version

Written by

Responses4