Skip to content

Migrate to ESM #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
CMCDragonkai opened this issue Dec 18, 2024 · 1 comment · Fixed by #6
Closed

Migrate to ESM #5

CMCDragonkai opened this issue Dec 18, 2024 · 1 comment · Fixed by #6
Labels
development Standard development

Comments

@CMCDragonkai
Copy link
Member

CMCDragonkai commented Dec 18, 2024 •
edited
Loading

Specification

This should be migrated to ESM, all upstream libraries is already ESM.

Also while doing this, we should conditionally import perf_hooks. Because browser environments would rely on the global performance API instead. And one of the whole points was to use top level awaits as way to switch between browser implementation or node implementation.

Additional context

Tasks

  1. Collate migration style from all repos
  2. Migrate this repo
  3. Release v2.0.0
@CMCDragonkai CMCDragonkai added the development Standard development label Dec 18, 2024
@linear Linear
Copy link

linear bot commented Dec 18, 2024

ENG-506 Migrate to ESM

@CMCDragonkai CMCDragonkai mentioned this issue Dec 18, 2024
Merged
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
development Standard development
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switching to ESM (and upgrading dependencies) MatrixAI/js-contexts
1 participant
@CMCDragonkai