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
exportdefault{/** Globs to analyze */globs: ['./src/temp/component.ts',],outdir: './',/** Run in watch mode, runs on file changes *//** Include third party custom elements manifests */dependencies: true,/** Output CEM path to `package.json`, defaults to true */packagejson: true,}
When using dependencies: true the analyzer crawls your module graph to find any third party dependencies to figure out where third party CEM's may be located. It should skip crawling local files though, because they'll already be crawled anyway. We should add a check in find-dependencies next to the builtin modules check to see if the imported file is a bare module specifier.
This shouldn't affect analysis of your CEM, however, the styles file and contents should still be included in your CEM. I checked and verified this locally.
Checklist
--dev
flag to get more information?CEM can't resolve dependencies.
component.ts
styles.ts
cem.config.mjs
custom-elements.json
The text was updated successfully, but these errors were encountered: