chore: rename dai-shi/waku => wakujs/waku for urls (#1312)

the redirect works, but this seems good and easy enough to do

Co-authored-by: Tyler <[email protected]>

Author: tylersayshi

README.md

@@ -4,7 +4,7 @@
 
 visit [waku.gg](https://waku.gg) or `npm create waku@latest`
 
-[![Build Status](https://img.shields.io/github/actions/workflow/status/dai-shi/waku/test.yml?branch=main&style=flat&colorA=000000&colorB=000000)](https://github.com/dai-shi/waku/actions?query=workflow%3ATest)
+[![Build Status](https://img.shields.io/github/actions/workflow/status/wakujs/waku/test.yml?branch=main&style=flat&colorA=000000&colorB=000000)](https://github.com/wakujs/waku/actions?query=workflow%3ATest)
 [![Version](https://img.shields.io/npm/v/waku?style=flat&colorA=000000&colorB=000000)](https://www.npmjs.com/package/waku)
 [![Downloads](https://img.shields.io/npm/dt/waku.svg?style=flat&colorA=000000&colorB=000000)](https://www.npmjs.com/package/waku)
 [![Discord Shield](https://img.shields.io/discord/627656437971288081?style=flat&colorA=000000&colorB=000000&label=discord&logo=discord&logoColor=ffffff)](https://discord.gg/MrQdmzd)
@@ -21,7 +21,7 @@ We recommend other frameworks for heavy ecommerce or enterprise applications. Wa
 
 ## Getting started
 
-Start a new Waku project with the `create` command for your preferred package manager. It will scaffold a new project with our default [Waku starter](https://github.com/dai-shi/waku/tree/main/examples/01_template).
+Start a new Waku project with the `create` command for your preferred package manager. It will scaffold a new project with our default [Waku starter](https://github.com/wakujs/waku/tree/main/examples/01_template).
 
 ```sh
 npm create waku@latest
@@ -145,7 +145,7 @@ To learn more about the modern React architecture, we recommend [Making Sense of
 
 Waku provides a minimal file-based “pages router” experience built for the server components era.
 
-Its underlying [low-level API](https://github.com/dai-shi/waku/blob/main/docs/create-pages.mdx) is also available for those that prefer programmatic routing. This documentation covers file-based routing since many React developers prefer it, but please feel free to try both and see which you like more!
+Its underlying [low-level API](https://github.com/wakujs/waku/blob/main/docs/create-pages.mdx) is also available for those that prefer programmatic routing. This documentation covers file-based routing since many React developers prefer it, but please feel free to try both and see which you like more!
 
 ### Overview
 
@@ -1075,8 +1075,8 @@ Streaming can be activated by setting environment variable `DEPLOY_AWS_LAMBDA_ST
 
 ## Community
 
-Please join our friendly [GitHub discussions](https://github.com/dai-shi/waku/discussions) or [Discord server](https://discord.gg/MrQdmzd) to participate in the Waku community. Hope to see you there!
+Please join our friendly [GitHub discussions](https://github.com/wakujs/waku/discussions) or [Discord server](https://discord.gg/MrQdmzd) to participate in the Waku community. Hope to see you there!
 
 ## Roadmap
 
-Waku is in active development and we’re seeking additional contributors. Check out our [roadmap](https://github.com/dai-shi/waku/issues/24) for more information.
+Waku is in active development and we’re seeking additional contributors. Check out our [roadmap](https://github.com/wakujs/waku/issues/24) for more information.

docs/guides/cloudflare.mdx

@@ -16,7 +16,7 @@ You should npm install the latest version of Cloudflare's build tool, [`wrangler
 
 After building, you can test your build by running `npx wrangler dev` or deploy it to Cloudflare using `npx wrangler deploy`.
 
-There is a [Cloudflare example in the Waku GitHub repository](https://github.com/dai-shi/waku/tree/main/examples/07_cloudflare).
+There is a [Cloudflare example in the Waku GitHub repository](https://github.com/wakujs/waku/tree/main/examples/07_cloudflare).
 
 ## Notes on Cloudflare's workerd Runtime
 
@@ -30,7 +30,7 @@ Note that the latest `nodejs_compat` mocks the Node `fs` module. Cloudflare does
 
 ## Setting Up TypeScript
 
-You can run `npx wrangler types --experimental-include-runtime` to generate a `worker-configuration.d.ts` file based on the settings in your `wrangler.toml`. This defines a global `Env` interface with your bindings. In the [Cloudflare example in the Waku GitHub repository](https://github.com/dai-shi/waku/tree/main/examples/07_cloudflare), a package.json script is included to run this command and update the types: `pnpm run build-cf-types`. To ensure that your types are always up-to-date, make sure to run it after any changes to your `wrangler.toml` config file.
+You can run `npx wrangler types --experimental-include-runtime` to generate a `worker-configuration.d.ts` file based on the settings in your `wrangler.toml`. This defines a global `Env` interface with your bindings. In the [Cloudflare example in the Waku GitHub repository](https://github.com/wakujs/waku/tree/main/examples/07_cloudflare), a package.json script is included to run this command and update the types: `pnpm run build-cf-types`. To ensure that your types are always up-to-date, make sure to run it after any changes to your `wrangler.toml` config file.
 
 ## Accessing Cloudflare Bindings, Execution Context, and Request/Response Objects
 
@@ -117,4 +117,4 @@ npm i --save-dev wrangler
 
 When starting the Waku dev server, we need to first start a wrangler/miniflare server and then pass them into the Hono app fetch.
 
-This can be done by creating a custom Waku plugin in your `waku.config.ts` file. Copy the `waku.cloudflare-dev-server.ts` and `waku.config.ts` to your project from [the Cloudflare example in the Waku GitHub repository](https://github.com/dai-shi/waku/tree/main/examples/07_cloudflare). Now when you run `waku dev`, you will be able to access Cloudflare env bindings and execution context on the Hono context.
+This can be done by creating a custom Waku plugin in your `waku.config.ts` file. Copy the `waku.cloudflare-dev-server.ts` and `waku.config.ts` to your project from [the Cloudflare example in the Waku GitHub repository](https://github.com/wakujs/waku/tree/main/examples/07_cloudflare). Now when you run `waku dev`, you will be able to access Cloudflare env bindings and execution context on the Hono context.

docs/guides/monorepo.mdx

@@ -26,7 +26,7 @@ export default defineConfig({
 });
 ```
 
-Ref: https://github.com/dai-shi/waku/issues/676
+Ref: https://github.com/wakujs/waku/issues/676
 
 ---
 

docs/guides/react-compiler.mdx

@@ -35,4 +35,4 @@ export default defineConfig({
 });
 ```
 
-Check out [a working example](../../examples/05_compiler), or visit the [StackBlitz demo](https://stackblitz.com/github/dai-shi/waku/tree/main/examples/05_compiler) with Waku v0.21.12 and up.
+Check out [a working example](../../examples/05_compiler), or visit the [StackBlitz demo](https://stackblitz.com/github/wakujs/waku/tree/main/examples/05_compiler) with Waku v0.21.12 and up.

docs/redirects.mdx

@@ -8,7 +8,7 @@ description: How to add HTTP redirects to your Waku project.
 
 Redirects are not handled by Waku directly. Instead, you can use either a custom middleware or the hosting environment to achieve that. The `<Link />` component does not deal with redirects either and will by default show the **404** page instead. To resolve this, you have to add an additional redirect for each redirected path, that points Waku to the correct `RSC` file. If there is a redirect from `/old` to `/new`, there also has to be one from `/RSC/old.txt`` to `/RSC/new.txt`to make the `<Link />` component`s smooth page transition work.
 
-> The `/RSC/` file naming convention is [subject to change](https://github.com/dai-shi/waku/discussions/929#discussioncomment-10825975) in future versions of Waku.
+> The `/RSC/` file naming convention is [subject to change](https://github.com/wakujs/waku/discussions/929#discussioncomment-10825975) in future versions of Waku.
 
 #### Redirect via middleware
 

e2e/create-pages.spec.ts

@@ -134,7 +134,7 @@ for (const mode of ['DEV', 'PRD'] as const) {
       ({ port, stopApp } = await startApp(mode));
     });
 
-    // https://github.com/dai-shi/waku/issues/1255
+    // https://github.com/wakujs/waku/issues/1255
     test('long suspense', async ({ page }) => {
       await page.goto(`http://localhost:${port}/long-suspense/1`);
       await expect(

e2e/fixtures/monorepo/packages/context-library/src/context-consumer.js

@@ -4,7 +4,7 @@
 import { createElement, useContext, useEffect, useState } from 'react';
 
 // Do not add '.js' extension to reproduce the issue
-// https://github.com/dai-shi/waku/pull/1162
+// https://github.com/wakujs/waku/pull/1162
 import { Context } from './context-provider';
 
 export const ContextConsumer = () => {

e2e/fixtures/monorepo/packages/dummy-library/src/index.js

@@ -1,3 +1,3 @@
 // Do not add '.js' extension to reproduce the issue
-// https://github.com/dai-shi/waku/pull/1143
+// https://github.com/wakujs/waku/pull/1143
 export * from './client';

e2e/fixtures/ssr-context-provider/README.md

@@ -1,3 +1,3 @@
 # SSR Context Provider
 
-To cover https://github.com/dai-shi/waku/issues/631 case
+To cover https://github.com/wakujs/waku/issues/631 case

examples/03_demo/src/components/header.tsx

@@ -7,7 +7,7 @@ export const Header = () => {
         <Link to="/">Waku pokemon</Link>
       </h2>
       <a
-        href="https://github.com/dai-shi/waku/tree/main/examples/03_demo"
+        href="https://github.com/wakujs/waku/tree/main/examples/03_demo"
         target="_blank"
         rel="noreferrer"
         className="text-sm hover:underline"

examples/03_demo/src/pages/index.tsx

@@ -12,7 +12,7 @@ export default async function HomePage() {
       <div className="flex h-full w-full flex-col items-center justify-center p-6">
         <div className="px-6">
           <a
-            href="https://github.com/dai-shi/waku/tree/main/examples/03_demo/src"
+            href="https://github.com/wakujs/waku/tree/main/examples/03_demo/src"
             target="_blank"
             rel="noreferrer"
             className="whitespace-nowrap text-xs font-bold hover:underline sm:text-base"

examples/06_form-demo/src/components/header.tsx

@@ -7,7 +7,7 @@ export const Header = () => {
         <Link to="/">Waku form demo</Link>
       </h2>
       <a
-        href="https://github.com/dai-shi/waku/tree/main/examples/06_form-demo"
+        href="https://github.com/wakujs/waku/tree/main/examples/06_form-demo"
         target="_blank"
         rel="noreferrer"
         className="text-sm hover:underline"

examples/33_promise/src/components/Counter.tsx

@@ -34,7 +34,7 @@ const Message = ({
   return (
     <ul>
       <li>count: {count}</li>
-      {/* We want show the usage without `use` but it causes a hydration error. https://github.com/dai-shi/waku/issues/202 */}
+      {/* We want show the usage without `use` but it causes a hydration error. https://github.com/wakujs/waku/issues/202 */}
       <li>delayedMessage: {use(delayedMessage)}</li>
     </ul>
   );

packages/create-waku/package.json

@@ -8,7 +8,7 @@
   ],
   "repository": {
     "type": "git",
-    "url": "https://github.com/dai-shi/waku.git",
+    "url": "https://github.com/wakujs/waku.git",
     "directory": "packages/create-waku"
   },
   "bin": {

packages/waku/package.json

@@ -12,7 +12,7 @@
   ],
   "repository": {
     "type": "git",
-    "url": "https://github.com/dai-shi/waku.git",
+    "url": "https://github.com/wakujs/waku.git",
     "directory": "packages/waku"
   },
   "exports": {

packages/waku/src/config.ts

@@ -7,7 +7,7 @@ export interface Config {
   /**
    * The base path for serve HTTP.
    * Defaults to  "/".
-   * TODO https://github.com/dai-shi/waku/issues/698
+   * TODO https://github.com/wakujs/waku/issues/698
    */
   basePath?: string;
   /**

packages/waku/src/lib/utils/swc.ts

@@ -6,7 +6,7 @@ export const parseOpts = (ext: string) => {
     } as const;
   }
   // We hoped to use 'typescript' for everything, but it fails in some cases.
-  // https://github.com/dai-shi/waku/issues/677
+  // https://github.com/wakujs/waku/issues/677
   return {
     syntax: 'ecmascript',
     jsx: ext.endsWith('x'),

packages/website/private/contents/post-001.mdx

@@ -13,7 +13,7 @@ RSC still relies on a framework (or at least a bundler) for implementation. Howe
 
 Waku is introduced as a minimal React framework that allows us to explore the core RSC capabilities and discover RSC best practices independent of traditional SSG/SSR strategies, which are optional opt-in functionalities.
 
-This website is developed with Waku. The [GitHub repository](https://github.com/dai-shi/waku) also includes various examples where you can learn how to use Waku and RSC features.
+This website is developed with Waku. The [GitHub repository](https://github.com/wakujs/waku) also includes various examples where you can learn how to use Waku and RSC features.
 
 ### Waku API
 

packages/website/private/contents/post-002.mdx

@@ -290,4 +290,4 @@ export const BlogLayout = async ({ children }) => {
 
 Now that a low-level API for creating layouts and pages is complete, we’re building a lightweight file-based “pages router” to further accelerate the work of Waku developers.
 
-Stay tuned for this and other features in the upcoming v0.20 release! In the meantime, please [give Waku a try](https://waku.gg) on non-production projects and join our friendly [GitHub discussions](https://github.com/dai-shi/waku/discussions) or [Discord server](https://discord.gg/MrQdmzd) to participate in the Waku community.
+Stay tuned for this and other features in the upcoming v0.20 release! In the meantime, please [give Waku a try](https://waku.gg) on non-production projects and join our friendly [GitHub discussions](https://github.com/wakujs/waku/discussions) or [Discord server](https://discord.gg/MrQdmzd) to participate in the Waku community.

packages/website/private/contents/post-003.mdx

@@ -331,6 +331,6 @@ export const getConfig = async () => {
 
 ## Next steps
 
-We will continue to add [additional features](https://github.com/dai-shi/waku/issues/24), improve [documentation](https://waku.gg), and work towards acheiving stability before the upcoming [React 19 release](https://react.dev/blog/2024/02/15/react-labs-what-we-have-been-working-on-february-2024#the-next-major-version-of-react).
+We will continue to add [additional features](https://github.com/wakujs/waku/issues/24), improve [documentation](https://waku.gg), and work towards acheiving stability before the upcoming [React 19 release](https://react.dev/blog/2024/02/15/react-labs-what-we-have-been-working-on-february-2024#the-next-major-version-of-react).
 
-In the meantime, please [star us on GitHub](https://github.com/dai-shi/waku) and [try Waku](https://waku.gg) on non-production projects. Then give us your feedback in our friendly [GitHub discussions](https://github.com/dai-shi/waku/discussions) and [Discord server](https://discord.gg/MrQdmzd). See you around!
+In the meantime, please [star us on GitHub](https://github.com/wakujs/waku) and [try Waku](https://waku.gg) on non-production projects. Then give us your feedback in our friendly [GitHub discussions](https://github.com/wakujs/waku/discussions) and [Discord server](https://discord.gg/MrQdmzd). See you around!

packages/website/private/contents/post-004.mdx

@@ -160,6 +160,6 @@ See the talk [What’s new in React 19?](https://www.youtube.com/watch?v=AJOGzVy
 
 We’re excited to see what you’ll build with Waku now that it fully supports server actions. Enjoy accelerated development of many common use cases such as form submissions, database operations, and much more!
 
-As always your feedback in our [GitHub discussions](https://github.com/dai-shi/waku/discussions) is much appreciated and you’re welcome to join us in our [Discord server](https://discord.gg/MrQdmzd) to share what you’re building.
+As always your feedback in our [GitHub discussions](https://github.com/wakujs/waku/discussions) is much appreciated and you’re welcome to join us in our [Discord server](https://discord.gg/MrQdmzd) to share what you’re building.
 
 Please stay tuned for our upcoming v0.22 release featuring API routes, which support even more complex or resource intensive server-side functionalities.

packages/website/src/components/navigation.tsx

@@ -194,6 +194,6 @@ const docs = [
 
 const links = [
   { to: '/blog', icon: 'book', label: 'Blog' },
-  { to: 'https://github.com/dai-shi/waku', icon: 'github', label: 'GitHub' },
+  { to: 'https://github.com/wakujs/waku', icon: 'github', label: 'GitHub' },
   { to: 'https://discord.gg/MrQdmzd', icon: 'discord', label: 'Discord' },
 ];

packages/website/src/pages/blog/[slug].tsx

@@ -88,7 +88,7 @@ export default async function BlogArticlePage({ slug }: BlogArticlePageProps) {
       </div>
       <div className="relative z-10 mx-auto mb-8 mt-16 flex w-full max-w-[80ch] justify-center sm:mb-0 lg:mt-32 xl:-right-[calc(296px/2)] 2xl:right-auto">
         <a
-          href="https://github.com/dai-shi/waku"
+          href="https://github.com/wakujs/waku"
           target="_blank"
           rel="noreferrer"
           className="text-shadow inline-block! -rotate-[5deg] transform whitespace-nowrap text-center font-serif text-3xl font-extrabold leading-none text-white transition-colors duration-300 ease-in-out hover:text-primary sm:mr-4 sm:text-6xl"

packages/website/src/pages/index.tsx

@@ -39,7 +39,7 @@ export default async function HomePage() {
       </div>
       <div className="relative z-10 mx-auto mb-8 mt-16 flex w-full max-w-[80ch] justify-center sm:mb-0 lg:mt-32 xl:-right-[calc(296px/2)] 2xl:right-auto">
         <a
-          href="https://github.com/dai-shi/waku"
+          href="https://github.com/wakujs/waku"
           target="_blank"
           rel="noreferrer"
           className="text-shadow inline-block! -rotate-[5deg] transform whitespace-nowrap text-center font-serif text-3xl font-extrabold leading-none text-white transition-colors duration-300 ease-in-out hover:text-primary sm:mr-4 sm:text-6xl"