chore(tsup.config.js): use banner to add 'use client' directive for nextjs

[manudeli]

related #5815

add tsup banner to add 'use client' directive for nextjs easily

reference

react-wrap-balancer

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
query	⬜️ Ignored (Inspect)	Visit Preview		Sep 5, 2023 0:39am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 38f9856. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

🟥 Failed Commands
nx affected --targets=test:eslint,test:lib,test:types,test:build,test:bundle

---

Sent with 💌 from NxCloud.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 38f9856:

Sandbox	Source
@tanstack/query-example-solid-basic-typescript	Configuration
@tanstack/query-example-svelte-basic	Configuration

[TkDodo]

hm, what does this banner do exactly, and why is this better than adding use client manually where we want it?

FYI, we actually want to move away from having use client on all files. Some files should use import client-only instead with a separate server entry point in package.json

I tried this here:

• Feature/react server #5633

Question is: how does the banner decide to which files a banner should go?

[TkDodo]

@manudeli I created a new PR for the import client-only feature:

• Feature/client only #5817

I think this would conflict with the banner ?

[TkDodo]

gonna close this because I don't think we want use-client everywhere.