Skip to content

Upgrading to pug is a breaking change #26

Description

@lbstr

Hello,

I appreciate you upgrading to pug, but it is a breaking change and requires a major version bump of your project. Since it looks like someone has already forked your projected to pug-bootstrap, maybe you should consider forgetting about pug and just leaving this project with jade support only. Your choice, of course.

In my case, I plan to update to pug soon, but I can't do it yet, so I must stay on jade. I had your project referenced as ^1.0.4, which I expected to stay on jade, but it looks like you upgraded to pug without bumping major versions, which broke my code.

Again, thank you for your work on this project. Let me know if you need any clarification on the problem described above.

Thank you,
Jared

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions