Skip to content

SWC_CORE semver complaint stablization  #5745

Open
@kwonoj

Description

@kwonoj

Describe the feature

Now swc_core can be used for the host / plugin both reasonably. However, we didn't reach the eventual goal we wanted to achieve yet:

  1. Prevent inter-package build / compatible errors

#5744 is a good example. User no longer lists all transitive dependencies to cause these kinds of problems, published swc_core can still hit internally across referenced packages.

This happens mostly when package version bump misses to pick up necessary changes. We should ensure this before publish happens.

  1. Avoid breaking changes

This is a bit more tricky, we need to find a way published version follows semver. Some changes are very straightforward to recognize as breaking changes, but some subtle changes can cause build / runtime error against previous versions unexpectedly.

Probably we'll need to setup some e2e regression tests with latest public version's plugin / host.

Babel plugin or link to the feature description

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions