Skip to content

library package with polymer elements needs a polymer transformer configuration #20673

Closed
@DartBot

Description

@DartBot

This issue was originally filed by @zoechi


A library package containing polymer elements needs a polymer transformer configuration otherwise the transformer doesn't process these elements.

see also http://stackoverflow.com/questions/25449308

Creating library packages for polymer elements is a common use case.
I don't think that a transformer config is necessary in this case is documented anywhere.

Packages like core-elements/paper-elements don't help much as model because they have the transformer config for the example pages. It's not obvious that the skeleton is necessary even when no entry pages do exist.

transformers:

  • polymer:
        entry_points:

I think there should be a warning message when polymer elements are imported from a package where this is missing.

I knew it and added it but it still didn't work.
It took me a while to discover that I had to kill pub serve to make the change take effect.

When I change the pubspec.yaml of the project pub serve is currently serving it kills itself but it doesn't when the pubspec.yaml of a path dependency is changed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-pkgUsed for miscellaneous pkg/ packages not associated with specific area- teams.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions