-
Notifications
You must be signed in to change notification settings - Fork 8
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I didn't look at the earlier commits in this repo but this PR in isolation looks good.
"out/*", | ||
"!out/*.test.*" | ||
], | ||
"exports": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks right to me
"next": ">=12.1.6", | ||
"react-dom": ">=16.0 <18.0", | ||
"replicache": ">=11.0.0", | ||
"pg-mem": ">=2.5.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OOC, why make pg-mem a peer dep?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this can be removed.
"types": "./out/frontend/index.d.ts", | ||
"import": "./out/frontend/index.js" | ||
}, | ||
"./out/backend/supabase": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this export for? I don't see it being used in the pending replicache-todo PR. I know that the frontend dir is pulling this in (kind of a hack), but I don't see why that would necessitate an export?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was having trouble getting next to ignore supabase backend dependencies for the frontend. However, I think this can be undone now now that everything is ESM
No description provided.