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

[legacy-framework] Move internal @blitzjs/core package into nextjs fork core (meta) #2857

Merged
merged 16 commits into from
Oct 19, 2021

Conversation

flybayer
Copy link
Member

@flybayer flybayer commented Oct 18, 2021

What are the changes and their implications?

We are working towards making our repo structure exactly match upstream nextjs. This is a two step process:

  1. Move all code into nextjs/ directory
  2. Move all code in nextjs/ up to top level

Once that is accomplished, we can merge upstream nextjs changes directly into this repo for a much better merge experience than the current intermediate repo we are using.

@flybayer flybayer changed the title More internal refactoring in effort to move all blitz code into nextjs/ directory Move @blitzjs/core package into nextjs fork core (meta) Oct 19, 2021
@flybayer flybayer marked this pull request as ready for review October 19, 2021 21:36
@flybayer flybayer requested a review from beerose as a code owner October 19, 2021 21:36
kodiakhq[bot]
kodiakhq bot previously approved these changes Oct 19, 2021
@flybayer flybayer changed the title Move @blitzjs/core package into nextjs fork core (meta) Move internal @blitzjs/core package into nextjs fork core (meta) Oct 19, 2021
@flybayer flybayer merged commit 6ac6176 into canary Oct 19, 2021
@flybayer flybayer deleted the fork-work branch October 19, 2021 22:22
@itsdillon itsdillon changed the title Move internal @blitzjs/core package into nextjs fork core (meta) [legacy-framework] Move internal @blitzjs/core package into nextjs fork core (meta) Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants