Skip to content
This repository was archived by the owner on Sep 2, 2023. It is now read-only.
This repository was archived by the owner on Sep 2, 2023. It is now read-only.

Feature: Transparent migration #105

Closed
@GeoffreyBooth

Description

@GeoffreyBooth

As I’m gradually migrating my CommonJS package to ESM one file at a time (see also #99 and #90), I can do so without needing to know or look up the module types of my dependencies. I don’t need to rely on dependencies’ READMEs or package.jsons or source code to know their module types, nor do I need to resort to trial and error.

This migration of my package does not cause a breaking change for any apps using my package’s API, nor for any apps importing my package as a dependency.

When I’m done migrating to all import and export statements, I can remove the Babel modules transform (or my entire build step) and the package functions the same as before.

Use cases 18, 20, 39, 40.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions