Skip to content

move layout components to @app/client#42

Open
AprilArcus wants to merge 1 commit intomainfrom
move-layout
Open

move layout components to @app/client#42
AprilArcus wants to merge 1 commit intomainfrom
move-layout

Conversation

@AprilArcus
Copy link
Copy Markdown
Owner

Moves <SharedLayout /> and everything that depends on it to the @app/client tree. Rationale: <SharedLayout /> needs to read process.env.T_AND_C_URL, which is a detail of the build that @app/components shouldn't know about.

When environment variable injection changes with Turbopack, we'll want to limit the blast radius.

The other option was passing termsAndConditionsUrl as a prop from @app/client into <SharedLayout /> everywhere we render it. But these layout components aren't logically reusable outside of their new locations in pages/ anyway, so it makes more sense to relocate them.

unblocks turbopack

Moves <SharedLayout /> and everything that depends on it to the
@app/client tree. Rationale: <SharedLayout /> needs to read
process.env.T_AND_C_URL, which is a detail of the build that
@app/components shouldn't know about.

When environment variable injection changes with Turbopack, we'll want
to limit the blast radius.

The other option was passing termsAndConditionsUrl as a prop from
@app/client into <SharedLayout /> everywhere we render it. But these
layout components aren't logically reusable outside of their new
locations in pages/ anyway, so it makes more sense to relocate them.

unblocks turbopack
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.

1 participant