8000 chore: switch build to esnext module type by sweatybridge · Pull Request #442 · supabase/postgres-meta · GitHub
[go: up one dir, main page]

Skip to content

chore: switch build to esnext module type #442

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.

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

Merged
merged 2 commits into from
Dec 23, 2022
Merged

chore: switch build to esnext module type #442

merged 2 commits into from
Dec 23, 2022

Conversation

sweatybridge
Copy link
Contributor
@sweatybridge sweatybridge commented Dec 23, 2022

What kind of change does this PR introduce?

build

What is the current behavior?

commonjs

What is the new behavior?

no need to support commonjs as pg-meta is purely server side

Additional context

Add any other context or screenshots.

@sweatybridge sweatybridge requested a review from a team as a code owner December 23, 2022 03:46
@sweatybridge sweatybridge mentioned this pull request Dec 23, 2022
1 task
@sweatybridge sweatybridge merged commit 52d6be5 into master Dec 23, 2022
@sweatybridge sweatybridge deleted the esnext branch December 23, 2022 07:40
@github-actions
Copy link

🎉 This PR is included in version 0.55.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This issue has been resolved in version 0.55.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@soedirgo
Copy link
Member
soedirgo commented Jan 4, 2023

FYI Studio imports @supabase/postgres-meta for types - not sure how this will affect that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0