Comments (7)
Do my answers clarify it a bit for you? I'd wish to be able to be more specific on the impact of version numbers. maybe we should ask Vesa :-)
from vscode-viva.
I think in there is no OOTB gupl task for it delivered with @microsoft/sp-build-core-tasks package
No that's correct, we've copied it from internet somewhere. It's picking up on an npm event I believe.
from vscode-viva.
Thanks @martinlingstuyl for adding an idea 👍.
A couple of things I would like to clarify:
- why do you usually update the version? Is it something you do just before the package publish to update it on the app catalog? Or is it something you just do regularly on adding every new feature and you just want to add this to the commit?
- do you always have aligned the package.json and package-solution.json? And if not what you would expect to happen on this task? Should one be overwritten to align with pacakge-solution.json? Or both should be increased?
- what number should be increased? Major? Minor? Or patch? Or should the extension ask for this option?
from vscode-viva.
I usually update the version with every change that I'm deploying. Just like we would do with the CLI. Some are patch versions, some minor and some major, depending on what I feel about it / semver :-)
I'm not entirely sure about the specifics, as I can't find the documentation about this, but versioning does seem to have impact on the version of the webpart that's loaded on SharePoint pages. Some time ago you would not really need to update the version per site, but these days it seems like it's really necessary to update on the site as well. (after deploying)
Also: I believe it's good practice to align the npm version with the project version. Check out this blog on the topic as well:
https://n8d.at/how-to-version-new-sharepoint-framework-projects
We use a gulp task to sync both numbers, so they are the same.
I'd suggest we need to be able to increase any part of the version. So patch, minor and major separately. Maybe three tasks, or one task that asks what version you want to upgrade.
from vscode-viva.
Do my answers clarify it a bit for you? I'd wish to be able to be more specific on the impact of version numbers. maybe we should ask Vesa :-)
Yes that helped a lot. Thanks for the additional info.
@VesaJuvonen is usually very busy (totally understandable), but if you have anything worth adding regarding versioning of spfx package please do 👍
from vscode-viva.
@martinlingstuyl I will set this feature for v3
In your answer I noticed
We use a gulp task to sync both numbers, so they are the same.
So you use a custom defined gulp task for it, right? I think in there is no OOTB gupl task for it delivered with @microsoft/sp-build-core-tasks package 🤔? Viva Toolkit base on those tasks as then we assume in every project they exist. We don't deliver any custom gulp tasks for every project.
from vscode-viva.
I think in there is no OOTB gupl task for it delivered with @microsoft/sp-build-core-tasks package
No that's correct, we've copied it from internet somewhere. It's picking up on an npm event I believe.
hmmm.. not possible path for this extension. but we may for sure prototype a different approach
from vscode-viva.
Related Issues (20)
- 💡 [Feature]: Add information about PnP npm packages to the SPFx project upgrade action. HOT 1
- 💡 [Feature]: The `Upgrade` and `Validate` actions could return also code tour response HOT 2
- 💡 [Feature]: Add more settings for the extension
- 💡 [Feature]: refactor the action naming HOT 4
- 🐞 [Bug]: Serve fails if folder path has space HOT 5
- 💡 [Feature]: Add support for SPFx 1.19.0 HOT 1
- 💡 [Feature]: Present solutions deployed per app catalog
- 💡 [Feature]: Show some additional setup steps in scaffolding form based on component type
- 💡 [Feature]: Add possibility to add custom additional step
- 💡 [Feature]: Add SPFx Fast Serve setup as additional step to the scaffolding form
- 💡 [Feature]: Sample gallery could have a filter by extension type when extension is selected HOT 2
- 🐞 Bug report: the name/description/tag filter does not work well and has lags HOT 3
- 💡 [Feature]: Refactor scaffolding form to smaller components HOT 8
- 💡 [Feature]: Refactor pipline scaffolding form to smaller components
- 💡 [Feature]: The pipline scaffolding form could allow to scaffold a run tests step
- 💡 [Feature]: Extend sample gallery with filter by supported hosts
- 💡 [Feature]: Correct the VS Code extension name in assets images HOT 3
- 💡 [Feature]: Add support for multiple SPFx projects
- 💡 [Feature]: Create model/service based on SharePoint list data HOT 3
- 💡 [Feature]: Add support for SPFx v1.19 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vscode-viva.