Skip to content

Current Node ESM format is not easily importable into TS projects with the current exports field #2

@trusktr

Description

@trusktr

I know how to make this work well, I've too much experience with Node ESM.

These are the issues I can help work through:

Screenshot 2023-06-02 at 10 59 47 PM Screenshot 2023-06-02 at 11 00 09 PM

Do you have any downstream projects that import wazum in its current state? If so, I'd like to take a look at those too so I know how to make the changes. The reason I ask is because in modern times, there isn't really a need to support old formats like UMD, etc. We can start fresh. Modern packages only need to publish ESM, and new projects should adapt. (IMO). But if you require support for old environments, it will be more maintenance burden (and issues).

This will be a bit of a change, will change the build and the output files completely, so that they are as idiomatic as possible (as close to regular vanilla ES as possible).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions