Tools: Does the latest version of WCT work with bare import specifiers?

Created on 1 May 2018  路  5Comments  路  Source: Polymer/tools

Just wondering if WCT supports the new bare import specifiers, I'm using [email protected]

All 5 comments

The prerelease has support via --module-resolution: https://github.com/Polymer/tools/blob/master/packages/web-component-tester/CHANGELOG.md#660-pre3---2018-03-21

If you install @next and run with --npm --module-resolution=node then bare specifiers should be rewritten to paths.

So: wct --npm --module-resolution=node?

So: wct --npm --module-resolution=node?

Yes. You can also set "npm:true" and "moduleResolution:node" in your wct.conf.json

Sorry, I'm getting this error: Error: wct-browser-legacy not installed. Please change --wct-package-name flag or install the package. Do I just need to do an npm install of wct-browser-legacy? Is there documentation for any of this yet?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

idoshamun picture idoshamun  路  3Comments

stramel picture stramel  路  4Comments

manolo picture manolo  路  4Comments

rwatts3 picture rwatts3  路  3Comments

NeoLegends picture NeoLegends  路  3Comments