Package type definitions not being found by VS Code

[rowan-lovejoy]

Expected Behavior

The esbuild-plugin-less package's type definitions are picked up by VS Code (also occurs in JetBrains Rider) and autocomplete is provided for its exports.

Actual Behavior

VS Code cannot find the type definitions for the package's exports; a squiggly red underline appears on the import path, and a message recommending the user to install a @types/esbuild-plugin-less file is displayed when hovering the path.

Steps to Reproduce the Problem

1. Create a new blank Node.js project in an empty folder using npm init -y
2. Install esbuild-plugin-less
3. Import any of the packages exports from "esbuild-plugin-less" inside a .ts file

Versions

• esbuild: 0.15.16
• esbuild-plugin-less: 1.3.0
• VS Code 1.82.2
• Platform: Windows 11

[iam-medvedev]

Thanks for pointing that out!

[github-actions]

🎉 This issue has been resolved in version 1.3.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[rowan-lovejoy]

Thanks for the prompt resolution!