You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vscode-uri dependency has been recently bumped to 1.0.7 and they included breaking changes in a patch release. See the commit: microsoft/vscode-uri@7f15d24
In particular, default export has been removed and changed to named export which results in errors:
error: cli runtime exception: TypeError: Cannot read property 'file' of undefinederror: TypeError: Cannot read property 'file' of undefined at new FsUrlResolver (/home/travis/build/vaadin/vaadin-time-picker/node_modules/polymer-analyzer/lib/url-loader/fs-url-resolver.js:48:55) at new PackageUrlResolver (/home/travis/build/vaadin/vaadin-time-picker/node_modules/polymer-analyzer/lib/url-loader/package-url-resolver.js:27:9) at ProjectConfig.<anonymous> (/home/travis/build/vaadin/vaadin-time-picker/node_modules/polymer-project-config/lib/index.js:301:33) at Generator.next (<anonymous>) at /home/travis/build/vaadin/vaadin-time-picker/node_modules/polymer-project-config/lib/index.js:20:71 at new Promise (<anonymous>) at __awaiter (/home/travis/build/vaadin/vaadin-time-picker/node_modules/polymer-project-config/lib/index.js:16:12) at ProjectConfig.initializeAnalyzer (/home/travis/build/vaadin/vaadin-time-picker/node_modules/polymer-project-config/lib/index.js:299:16) at Object.<anonymous> (/home/travis/build/vaadin/vaadin-time-picker/node_modules/polymer-cli/lib/lint/lint.js:74:82)
In the meanwhile, as a workaround we have to pin to =1.0.6 explicitly.
The text was updated successfully, but these errors were encountered:
The
vscode-uri
dependency has been recently bumped to1.0.7
and they included breaking changes in a patch release. See the commit: microsoft/vscode-uri@7f15d24In particular, default export has been removed and changed to named export which results in errors:
In the meanwhile, as a workaround we have to pin to
=1.0.6
explicitly.The text was updated successfully, but these errors were encountered: