Skip to content

fix: update locked glimpseui version to 0.6.2#5

Open
yasuhito wants to merge 1 commit intobadlogic:mainfrom
yasuhito:fix/glimpseui-lockfile
Open

fix: update locked glimpseui version to 0.6.2#5
yasuhito wants to merge 1 commit intobadlogic:mainfrom
yasuhito:fix/glimpseui-lockfile

Conversation

@yasuhito
Copy link
Copy Markdown

@yasuhito yasuhito commented Apr 12, 2026

Summary

  • update the locked glimpseui version in package-lock.json from 0.6.0 to 0.6.2
  • ensure the lockfile resolves to a package that includes the Chromium backend

Background

  • as reported in is package-lock.json intentionally committed? #4, glimpseui 0.6.0 can fail at runtime because src/chromium-backend.mjs is missing
  • package.json already allows newer 0.6.x releases via ^0.6.0, so only the lockfile needs to change

Verification

  • npm ls glimpseui -> glimpseui@0.6.2
  • node --input-type=module -e "import('glimpseui').then(m => console.log(JSON.stringify(m.getNativeHostInfo())))" resolves a host config pointing at src/chromium-backend.mjs

Fixes #4

@yasuhito yasuhito changed the title fix: package-lock.json の glimpseui を 0.6.2 に更新 fix: update locked glimpseui version to 0.6.2 Apr 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

is package-lock.json intentionally committed?

1 participant