Package update information text seems borked upon todays VScode update

[sammcj]

Getting some funky text distortion on npm outdated's update information after updating VSCode today:

• All other plugins seem to be operating normally.
• No other plugins provide update text for npm packages that could be clashing.
• macOS 13.4.1
• VSCode 1.80.0

Is this a known issue?

[rentalhost]

Is this happening consistently? The vscode has some difficulty handling colored text like this, and I had reported it to them, but they simply ignored it and said it's intended behavior.

As an alternative, there is an option in the extension to disable the color system (search for npm-outdated.decorations in the settings). However, the recent changes in PR #22 may potentially solve this issue.

Since it hasn't been reviewed and approved yet, I'll provide an option here to download it and manually install it in vscode.

https://drive.google.com/file/d/1AxQFX09m_eD86_dWuF0mHN4EZ3g3afAc/view?usp=sharing

[sammcj]

Yeah it is consistent and reproducible.

I wouldn't be surprised if it clashed with one of the many other VSCode extensions that format text - but haven't been able to pin down which one if so (and haven't added any new extensions).

Thanks for alerting me to npm-outdated.decorations - setting that to disabled resolves the issue for me - not ideal but at least I can read it now!

[rentalhost]

@sammcj Do you think you can create a reduced test package? I believe package.json, package-lock.json (or similar) might be reproducible.

[sammcj]

Sure thing, here's a zip with package.json, package-lock.json where the text gets overlapped.

Archive.zip

Enabled VScode packages:

• NPM Outdated
• NPM Intellisense
• Error Lens
• Better Comments
• ESLint

And confirming that setting "npm-outdated.decorations": "disabled" fixes the issue.

[rentalhost]

Unfortunately, I couldn't reproduce it in either the current version or the PR #22 version. Both worked perfectly. It seems that there is a conflict with the Error Lens extension.

I believe this bug should be reported directly to the vscode team (I've never had much luck with them, but who knows...). In the meantime, perhaps you can keep the "npm-outdated.decorations": "disabled" configuration or temporarily configure Error Lens to exclude ^Newer version of at settings.

Additionally, thank you, I didn't know about Error Lens, and it seems quite useful.

[sammcj]

ahhhh, so npm-outdated is showing those messages as a type of error, and ErrorLens will be those errors up (again)?

If so - I agree, it sounds like it's a core vscode issue where multiple error annotations shouldn't overlap.

ErrorLens is so, so useful - just perhaps not in this specific case 😄.

Sorry for wasting your time on this one! I'll close this off and might log a bug with VScode (at which point I'll link to this).

[sammcj]

Oh and a little tip with ErrorLens - I'd highly recommend setting it to show just warn and error level otherwise it can be pretty noisy.