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

feat(nextjs): Support rendering ClerkProvider in client components #1840

Merged
merged 7 commits into from
Oct 18, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/gorgeous-countries-appear.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@clerk/nextjs': patch
---

Update `<ClerkProvider />` to work in client components within the app router. This allows rendering of the provider in client components, previously the pages router provider was being imported and throwing an error.
12 changes: 11 additions & 1 deletion integration/models/application.ts
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ export const application = (config: ApplicationConfig, appDirPath: string, appDi
const now = Date.now();
const stdoutFilePath = path.resolve(appDirPath, `e2e.${now}.log`);
const stderrFilePath = path.resolve(appDirPath, `e2e.${now}.err.log`);
let buildOutput = '';

const self = {
name,
Expand Down Expand Up @@ -70,7 +71,16 @@ export const application = (config: ApplicationConfig, appDirPath: string, appDi
},
build: async () => {
const log = logger.child({ prefix: 'build' }).info;
await run(scripts.build, { cwd: appDirPath, log });
await run(scripts.build, {
cwd: appDirPath,
log: (msg: string) => {
buildOutput += `\n${msg}`;
log(msg);
},
Comment on lines +76 to +79
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Captures and makes the build output available by way of app.buildOutput. This allows us to assert on the output.

});
},
get buildOutput() {
return buildOutput;
},
serve: async (opts: { port?: number; manualStart?: boolean } = {}) => {
const port = opts.port || (await getPort());
Expand Down
12 changes: 7 additions & 5 deletions integration/tests/global.teardown.ts
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,13 @@ setup('teardown long running apps', async () => {
console.log('Skipping cleanup');
return;
}
const runningAppsFoundInStateFile = Object.values(stateFile.getLongRunningApps());
const matchingLongRunningApps = appConfigs.longRunningApps.getByPattern(
runningAppsFoundInStateFile.map(app => app.id),
);
await Promise.all(matchingLongRunningApps.map(app => app.destroy()));
const runningAppsFoundInStateFile = Object.values(stateFile.getLongRunningApps() ?? {});
if (runningAppsFoundInStateFile.length > 0) {
const matchingLongRunningApps = appConfigs.longRunningApps.getByPattern(
runningAppsFoundInStateFile.map(app => app.id),
);
await Promise.all(matchingLongRunningApps.map(app => app.destroy()));
}
stateFile.remove();
console.log('Long running apps destroyed');
});
72 changes: 72 additions & 0 deletions integration/tests/next-build.test.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@
import { expect, test } from '@playwright/test';

import type { Application } from '../models/application';
import { appConfigs } from '../presets';

test.describe('next build @nextjs', () => {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nikosdouvlis Any feedback on the test? 🙏

test.describe.configure({ mode: 'parallel' });
let app: Application;
const output = [];

test.beforeAll(async () => {
app = await appConfigs.next.appRouter
.clone()
.addFile(
'src/app/provider.tsx',
() => `'use client'
import { ClerkProvider } from "@clerk/nextjs"

export function Provider({ children }: { children: any }) {
return (
<ClerkProvider>
{children}
</ClerkProvider>
)
}`,
)
.addFile(
'src/app/layout.tsx',
() => `import './globals.css';
import { Inter } from 'next/font/google';
import { Provider } from './provider';

const inter = Inter({ subsets: ['latin'] });

export const metadata = {
title: 'Create Next App',
description: 'Generated by create next app',
};

export default function RootLayout({ children }: { children: React.ReactNode }) {
return (
<Provider>
<html lang='en'>
<body className={inter.className}>{children}</body>
</html>
</Provider>
);
}
`,
)
.commit();
await app.setup();
await app.withEnv(appConfigs.envs.withEmailCodes);
await app.build();
});

test.afterAll(async () => {
await app.teardown();
});

test('When <ClerkProvider /> is used as a client component, builds successfully and does not force dynamic rendering', () => {
const dynamicIndicator = 'λ';

/**
* Using /_not-found as it is an internal page that should statically render by default.
* This is a good indicator of whether or not the entire app has been opted-in to dynamic rendering.
*/
const notFoundPageLine = app.buildOutput.split('\n').find(msg => msg.includes('/_not-found'));

expect(notFoundPageLine).not.toContain(dynamicIndicator);
});
});
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@
"test:ci": "FORCE_COLOR=1 turbo test --concurrency=${TURBO_CONCURRENCY:-80%}",
"test:integration:base": "DEBUG=1 npx playwright test --config integration/playwright.config.ts",
"test:integration:generic": "E2E_APP_ID=react.vite.* npm run test:integration:base -- --grep @generic",
"test:integration:nextjs": "E2E_APP_ID=next.appRouter.withEmailCodes npm run test:integration:base -- --grep @generic",
"test:integration:nextjs": "E2E_APP_ID=next.appRouter.withEmailCodes npm run test:integration:base -- --grep \"@generic|@nextjs\"",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed in the initial RFC, I added a @nextjs tag as well.

"test:integration:remix": "echo 'placeholder'",
"test:integration:deployment:nextjs": "DEBUG=1 npx playwright test --config integration/playwright.deployments.config.ts",
"clean": "turbo clean",
Expand Down
3 changes: 2 additions & 1 deletion packages/nextjs/src/app-router/client/ClerkProvider.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ import React from 'react';
import { ClerkNextOptionsProvider } from '../../client-boundary/NextOptionsContext';
import { useSafeLayoutEffect } from '../../client-boundary/useSafeLayoutEffect';
import type { NextClerkProviderProps } from '../../types';
import { mergeNextClerkPropsWithEnv } from '../../utils/mergeNextClerkPropsWithEnv';
import { useAwaitableNavigate } from './useAwaitableNavigate';

declare global {
Expand Down Expand Up @@ -33,7 +34,7 @@ export const ClientClerkProvider = (props: NextClerkProviderProps) => {
};
}, []);

const mergedProps = { ...props, navigate };
const mergedProps = mergeNextClerkPropsWithEnv({ ...props, navigate });
return (
<ClerkNextOptionsProvider options={mergedProps}>
{/*// @ts-ignore*/}
Expand Down
19 changes: 19 additions & 0 deletions packages/nextjs/src/client-boundary/ClerkProvider.tsx
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
'use client';

import { useRouter } from 'next/compat/router';
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a stable export we can rely on being available?

Or are we reaching into private APIs here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe it is stable and reliable, based on PR: vercel/next.js#42502.

import React from 'react';

import { ClientClerkProvider } from '../app-router/client/ClerkProvider';
import { ClerkProvider as PageClerkProvider } from '../pages/ClerkProvider';
import { type NextClerkProviderProps } from '../types';

/**
* This is a compatibility layer to support a single ClerkProvider component in both the app and pages routers.
*/
export function ClerkProvider(props: NextClerkProviderProps) {
const router = useRouter();

const Provider = router ? PageClerkProvider : ClientClerkProvider;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The solution here makes perfect sense to me :)
Do you think we could merge the two client providers into one? I took a quick look and they look pretty similar.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nikosdouvlis possibly, the difficulty is they rely on the two different router hooks, which is why we need this layer. We could abstract the dependency on the router into a prop and use this layer to compute the prop to pass down to single provider.


return <Provider {...props} />;
}
2 changes: 1 addition & 1 deletion packages/nextjs/src/components.client.ts
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
export { ClerkProvider } from './pages/ClerkProvider';
export { ClerkProvider } from './client-boundary/ClerkProvider';
export { SignedIn, SignedOut } from './client-boundary/controlComponents';
Loading