analyzeDependencies not work in bundle api?

[noyobo]

// a.css
@import url('./b.css');

.a {
    color: red;
}

const result = await bundle({
    filename: 'a.css',
    sourceMap: true,
    analyzeDependencies: true,
  });

console.log(result.dependencies) // []

lightningcss v1.21.0

[devongovett]

That's because the imports are already inlined when bundling, so the output doesn't contain any dependencies anymore. analyzeDependencies isn't really meant to be used with the bundle api.

[devongovett]

Actually I think omitting this entirely was kinda incorrect. Other types of dependencies can still be found during bundling, such as url() references. Only @import won't be encountered because it is already bundled. I'm going to revert the PR that omitted this. Sorry about that, I didn't think about this hard enough.

[noyobo]

I actually expect @import dependencies to be analyzed as well, since that's a must when you need to listen for file changes to trigger a rebuild. @devongovett

[devongovett]

I think that's a slightly different requirement. analyzeDependencies returns unresolved dependencies, e.g. the verbatim string passed to @import. But after bundling, these have been resolved to actual files, so you'd want those instead. One way of doing that would be to look at the generated source map and inspect the sources list. Another way would be to use a custom resolver that tracks which files are read.