Skip to content
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

Billable: Create invoice services #36

Merged
merged 14 commits into from
Jan 13, 2025
Merged

Billable: Create invoice services #36

merged 14 commits into from
Jan 13, 2025

Conversation

peterp
Copy link
Contributor

@peterp peterp commented Jan 8, 2025

  • Stub invoice service.
  • Display invoice data from datatabase.

@peterp peterp marked this pull request as ready for review January 13, 2025 07:57
@peterp peterp merged commit 866ec6e into main Jan 13, 2025
justinvdm added a commit that referenced this pull request Jan 13, 2025
 ## Problem
I added a fix in #36 (44632d7) that caused us to always resolve react to a custom
build of react. This custom build caters for the
fact that RSC and SSR are sharing a runtime.

However, I accidentally made the client side bundling also use this custom build of react, rather than normal react.

 ## Solution

I've added a plugin that allows us to alias react to the custom build of react only for the worker side, but leave it alone on the client side.

 ## Note
While fixing this, I discovered that the current way of having RSC and SSR share a single react build will not work for all things. For example,
if there is a `use()` call in SSR-rendered code, we will end up with an issue because RSC is expecting its `use()`` and not the SSR `use()`.

I'll work on fixing this in a future PR.
@justinvdm justinvdm mentioned this pull request Jan 13, 2025
justinvdm added a commit that referenced this pull request Jan 13, 2025
## Problem
I added a fix in #36 (44632d7) that caused us to always resolve react to a custom
build of react. This custom build caters for the
fact that RSC and SSR are sharing a runtime.

However, I accidentally made the client side bundling also use this custom build of react, rather than normal react.

 ## Solution

I've added a plugin that allows us to alias react to the custom build of react only for the worker side, but leave it alone on the client side.

 ## Note
While fixing this, I discovered that the current way of having RSC and SSR share a single react build will not work for all things. For example,
if there is a `use()` call in SSR-rendered code, we will end up with an issue because RSC is expecting its `use()`` and not the SSR `use()`.

I'll work on fixing this in a future PR.
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