Reason: The import was refering to the local source of the lib, instead of the published one (from the same place). The commit that changed the path was a mistake, probably occuring while I was updating the lib with new codicons, and tests were made using the local source prior to publishing to npm.
Environment/version
Steps to reproduce
vscode-ext-codicons
Reason: The import was refering to the local source of the lib, instead of the published one (from the same place). The commit that changed the path was a mistake, probably occuring while I was updating the lib with new codicons, and tests were made using the local source prior to publishing to npm.