akira-toriyama / next.js-tpl Goto Github PK

scss は、ネストすると可読性がつらい
Linaria を試す

https://zenn.dev/chot/articles/next-layout-for-admin-page

検証

}

// todo 検証
// TODO 検証

523b6416ba3919c3563a25ddb94318a7524c8ad6

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

https://api.github.com/akira-toriyama/next.js-tpl/blob/a0ad2ef66f3d8bd9c4580b14f98e34966ea68043/next.config.js#L6

const { withKumaUI } = require("@kuma-ui/next-plugin");

/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  // TODO やめる
  pageExtensions: ["page.tsx"],
  compiler: {
    reactRemoveProperties: true,
  },
};

module.exports = withKumaUI(nextConfig);

https://nextjs.org/docs/app/building-your-application/routing/intercepting-routes

https://api.github.com/akira-toriyama/next.js-tpl/blob/1f3e6d6321321ca16d8f422345810b978cf2ffd3/app/layout.tsx#L27

);

export default Layout;

// TODO チャクラ 適用

https://zenn.dev/siino/articles/b42d658af571f0

// ちゃくらui
// コンテンツプレースホルダー
// #2151
// nextjs dbなども追加
loading いる？

useMediaquery が扱いやすい

https://nextjs.org/docs/app/building-your-application/routing/middleware

vitest-dev/vitest#1241

/// <reference types="vitest" />
import { defineConfig } from "vite";
import { configDefaults } from "vitest/config";

import react from "@vitejs/plugin-react";
import path from "path";

export default defineConfig({
  /**
   * https://github.com/tajo/ladle/issues/100#issuecomment-1192413254
   */
  define: {
    "process.env": process.env,
  },
  // @ts-expect-error -- ???
  plugins: [react()],
  test: {
    environment: "jsdom",
    exclude: [...configDefaults.exclude, "snapshot/snapshot.test.ts"],
    coverage: {
      all: true,
      include: ["src/**/*.{ts,tsx}"],
      exclude: [
        "**/*.stories.tsx",
        "**/*.gql.generated.ts",
        "**/*.gql.ts",
        "**/dao.ts",
        "src/infra/graphql/types.ts",
        "src/ui/provider/Wrapper.tsx",
        "src/ui/provider/ReactQuery.tsx",
        "src/ui/provider/ErrorBoundary.tsx",
        "src/infra/env.ts",
      ],
      provider: "istanbul",
    },
  },
  resolve: {
    alias: {
      "~": path.join(__dirname, "./src"),
    },
  },
  server: {
    /**
     * https://github.com/tajo/ladle/blob/main/e2e/playwright/vite.config.ts
     */
    open: "none",
  },

  preview: {
    /**
     * https://github.com/tajo/ladle/blob/main/e2e/playwright/vite.config.ts
     */
    open: "none",
  },
});

// TODO カバレッジしきい値
// https://github.com/vitest-dev/vitest/issues/1241

await expect(page).toHaveURL("/items");

https://api.github.com/akira-toriyama/next.js-tpl/blob/483a81631ba6ec42f8fac167c3dfa0072e341145/app/items/[id]/edit/page.spec.tsx#L63

    .fill(service.formParam.body.placeholder);
  await page.getByRole("button", { name: "submit" }).click();

  // TODO テスト不能
  // await expect(page).toHaveURL("/items");
});

https://api.github.com/akira-toriyama/next.js-tpl/blob/46508f04be1fc18256c1cb6a5a565bab18447275/src/ui/domain/item/common/hook/useFetch/useFetch.ts#L5

import { useQuery } from "@tanstack/react-query";
import * as dao from "./coLocation/dao";
import type * as commonType from "../../common.type";

// TODO keys.ts
export const useFetch = (p: commonType.OuterProps) =>
  useQuery(["Common", { id: p.id }], () => dao.find(p));

https://api.github.com/akira-toriyama/next.js-tpl/blob/99db1241b25d872bebdaa4eb7150fac7f6620579/pages/_app.page.tsx#L24

);

export default Page;

// TODO tsconfig bump https://github.com/tsconfig/bases/pull/161

sp, pc などのメディアクエリ対応

CSS in JS を使うので、 useMediaquery を使うのでよさそう。
下記の書き方は、可読性に限界を感じる...

// pc
@media screen and (width >= 64em) {
}

// tablet
@media screen and (width >= 48em) and (width < 64em) {
}

// sp
@media screen and (width < 48em) {
}

selectors は いらないかも？

https://api.github.com/akira-toriyama/next.js-tpl/blob/89df2b1e61f1410ba862fc060eca949c4f630f18/app/items/loading.tsx#L1

// TODO コンテンツプレースホルダーを適用 or やめる
import type { NextPage } from "next";
import * as presenter from "~/ui/domain/items/presenter";

https://api.github.com/akira-toriyama/next.js-tpl/blob/1f3e6d6321321ca16d8f422345810b978cf2ffd3/app/items/[id]/detail/page.spec.tsx#L24

  );

  await page.goto("/items/1/detail");
  // TODO CI でエラー
  await page.getByText("編集へ").first().click();
  await expect(page).toHaveURL("/items/1/edit");
});

hoge fuga

      )
      .exhaustive()
  );
// TODO どうしましょ？
// hoge fuga

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀