Closed flybayer closed 2 years ago
In order to streamline nextjs upgrades, we need to move all blitz package code into the nextjs fork. Once that is finished, we can move the nextjs fork to the top level and then merge nextjs upgrades directly into this repo.
packages/babel-preset
packages/display
packages/installer
packages/generator
packages/cli
packages/server
next
packages/blitz
nextjs/packages/next
blitz
next/*
blitz/*
test/integration
nextjs/test/integration/
nextjs/
nextjs
I was thinking about that because with this coming: https://twitter.com/leeerob/status/1458846513451384832
What do you want and why?
In order to streamline nextjs upgrades, we need to move all blitz package code into the nextjs fork. Once that is finished, we can move the nextjs fork to the top level and then merge nextjs upgrades directly into this repo.
packages/babel-preset
@flybayer https://github.com/blitz-js/blitz/pull/2903packages/display
(some or all already in next package) @beerose https://github.com/blitz-js/blitz/pull/2989packages/installer
packages/generator
- wait for https://github.com/blitz-js/blitz/pull/2679packages/cli
packages/server
(will basically become obsolete once cli package is moved)next
binary and pass all argspackages/blitz
nextjs/packages/next
package becomes the main entry point for CLI and everythingnextjs/packages/next
toblitz
in package.json name field onlynext/*
toblitz/*
for compatibility with people converting nextjs projects to blitztest/integration
tests intonextjs/test/integration/
nextjs/
nextjs
to top level