danabra.mov / overreacted
my blog https://overreacted.io
53
fork

Configure Feed

Select the types of activity you want to include in your feed.

twk

Dan Abramov c66e9a56 b1b652d8

+1 -1
+1 -1
public/how-imports-work-in-rsc/index.md
··· 844 844 845 845 ### In Conclusion 846 846 847 - RSC does not shy away from the fact that both the backend and the frontend each have its own module system. It works exactly like traditional JavaScript codebases that reuse some code between the frontend and the backend, where reused code effectively exists on both sides. What RSC adds on top are just two mechanisms: 847 + RSC does not shy away from the fact that the backend and the frontend each have their own module system. It works exactly like traditional JavaScript codebases that reuse some code between the frontend and the backend, where reused code effectively exists on both sides. What RSC adds on top are just two mechanisms: 848 848 849 849 - The `import 'client-only'` and `import 'server-only'` poison pills that let some individual modules declare they *must not be brought* into the other world. 850 850 - The `'use client'` and `'use server'` directives that let you *refer* to the modules from the other world and pass data to them without *bringing them in*.