Request: make BuildImporter a public API

[refi64]

I want to add Sass support to VueDart 0.4, and right now I'm importing this project's BuildImporter, even though it's technically private please don't kill me. However, I figured this might be something other projects may want, too, so I was wondering what the chances would be to make BuildImporter "officially" public...

[nshahan]

I'm not opposed to the idea, but I am more curious why you are not just using the exposed builder?

[refi64]

The reason is that I'm compiling inline Sass inside of the Vue templates, e.g.:

<style scoped lang="scss">
/* etc */
</style>

[nshahan]

I am reluctant to expose it since it will legitimize adding a dependency on sass_builder for packages that only want to reuse the Importer.

By adding the dependency you are signalling to build_runner to automatically run sass_builder on your package during the build which might unnecessarily add to the build time.

sass_builder/build.yaml

Line 5 in 888e8b2

auto_apply: dependents

I'm still thinking about how we should handle this. Maybe we should expose the Importer in a different package.

[nshahan]

I'm thinking for now that if we move it out of lib/src we just recommend that anyone depending on the package just to import that file should disable the sass_builder on their package. Does that make sense?

Something like:

targets:
  vue:
...
    builders:
      sass_builder|sass_builder:
        enabled: False

[refi64]

Honestly, I think that would be entirely fine. Realistically I have no doubt that a bunch of VueDart projects will end up using Sass anyway...