You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After looking into this and brainstorming ways of supporting it, I don’t think we can support this at the moment. There’s a number of issues that make this challenging to tackle.
The biggest problem is that we version framework scaffolding tools (like create-react-app), not the frameworks themselves.
In many cases, these tools don’t even version the frameworks. Here’s a few examples of package.json files where a framework version is nowhere to be found:
Furthermore, most frameworks don’t have a coordinated matching version with their scaffolding tools. For example, the latest version of create-svelte as of this writing is 5.1.1, where the latest version of svelte is 4.2.2.
Most of these tools actually pull from template repos to copy their initial files. These templates will have a package.json that actually pins the version of the framework.
Because of these factors, it’s quite difficult to determine the mapping between the version of frameworks and their scaffolding tools.
We considered inspecting the artifacts of our e2e runs on dependabot PRs, inspecting the resultant package.json for the version and committing it along with the version bump. Even this won’t quite give us a correct result however, since the framework version isn’t really deterministic for multiple runs of the same scaffolding tool. This is because many of them allow you to select or specify a template, which may have different framework version. Not only that, but these templates are often pulled directly from github as raw files, not installed as a dependency via npm, meaning they aren’t actually versioned by the scaffolding tools and can change at any time.
Without a viable strategy to handle this, it seems as if it’s better to not tell users a version than to tell them a version that’s possibly incorrect.
Describe the solution
Currently we list only names, but it's unclear to users what they'll get:
Could we please add a major version number after each item in the menu?
The text was updated successfully, but these errors were encountered: