Skip to content

Conversation

ZeroWave022
Copy link
Contributor

The (default) exports removed are usually specified like this when using the "exports" field:

"exports": {
  ".": {
    "require": "./dir/main.js",
    "import": "./dir/main.js",
    "types": "./dir/main.d.ts"
  }
}

However, using this approach for this package is unnecessary and can cause problems later down the line.
As new versions of the tip.cc API are released, users of this package will need to specify they want to use the new version. This is likely the safest approach, instead of a dynamic default import.

This is a breaking change (of something that shouldn't be implemented in the first place), and tipccjs/tipcc.js will be updated with a hotfix accordingly.

This forces package users to specify API version when importing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants