fix(smartui): install SmartUI CLI 4.1.77 by default (TE-22391) - #16
Open
chaitanyas-maker wants to merge 1 commit into
Open
fix(smartui): install SmartUI CLI 4.1.77 by default (TE-22391)#16chaitanyas-maker wants to merge 1 commit into
chaitanyas-maker wants to merge 1 commit into
Conversation
Pin @lambdatest/smartui-cli to ^4.1.77 and tag install commands @latest so samples no longer bootstrap an outdated CLI. Refs TE-22391 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H5pDePdJgs3Ms7qpjKc4kU
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part of TE-22391.
Users following this sample could end up on an outdated SmartUI CLI, which is a known cause of visual rendering issues and a recurring source of support tickets.
What was wrong
Running
npm installin this repository resolved@lambdatest/smartui-clito 2.0.3, not the current 4.1.77, becausepackage.jsonalready saidlatest, but the committedpackage-lock.jsonpinned 2.0.3 and won.Note that this is not visible from the README. The README install command was already correct; the stale version came from the dependency manifest.
Changes
package.json: pin@lambdatest/smartui-clito^4.1.77package-lock.json: regenerated sonpm cistays consistent with the manifest. The only direct dependency that moves is@lambdatest/smartui-cli; the rest of the diff is transitive resolution.Verification
npm install --dry-run, before and after this change:A note on
@latestAdding
@latestto a barenpm install <package>does not change what gets installed: npm already resolves an unversioned package name to thelatestdist-tag. It is included here for explicitness, but on its own it does not fix the stale-CLI problem. The dependency manifest is what actually determines the installed version.🤖 Generated with Claude Code
https://claude.ai/code/session_01H5pDePdJgs3Ms7qpjKc4kU