`registerCSS` rejects the `debug: "verbose"` it passes on, and never calls a `logger` it is given
メンテナーはふだん 5 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 2/5
- 見積もり時間
- 1〜3時間
- 初心者へのやさしさ
- 78/100
- issue の種類
- バグ
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- react-native, typescript
調査の方向性
src/jest/index.tsから始めて、registerCSSがオプションの型をどのように定義し、compileWithAutoDebugに渡すかを追ってください。再現ケースにはsrc/__tests__/native/jest-helper-options.test.tsが示されており、2つの確認項目があります。debug: "verbose"は型チェックに通ること、指定したロガーがcompileと同じメッセージを受け取ることです。
索引モデルが issue の本文から書いたものです。
説明
Before submitting a new issue
- I tested using the latest version of the library, as the bug might be already fixed.
- I tested using a supported version of react native.
- I checked for possible duplicate issues, with possible answers.
Bug summary
registerCSS(css, options) in src/jest/index.ts types options as CompilerOptions & { debug?: boolean } and passes them to compileWithAutoDebug, which takes debug?: boolean | "verbose" and prints the rule log only for "verbose", so registerCSS(css, { debug: "verbose" }) fails to type-check. Both accept CompilerOptions.logger, and compileWithAutoDebug returns compile(css, { ...options, logger }), which replaces it, so a logger handed to either is never called.
The test harnesses' registerCSS(output, { debug: Boolean(debug) }), reported in #545 and nativewind/nativewind#1878, turns "verbose" into true at that call.
Library version
main at df32ce3
Environment info
System:
OS: Windows 11 10.0.26300
CPU: "(32) x64 AMD Ryzen 9 9950X3D 16-Core Processor "
Memory: 160.57 GB / 255.67 GB
Binaries:
Node:
version: 26.12.1
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 4.9.2
path: C:\Users\<user>\AppData\Roaming\npm\yarn.CMD
npm:
version: 12.2.1
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
Versions:
- 10.0.19041.0
- 10.0.26100.0
IDEs:
Android Studio: AI-262.9437.185.2621.16467767
Visual Studio: Not Found
Languages:
Java:
version: 17.0.20.1
path: C:\Program Files\Microsoft\jdk-17.0.20.101-hotspot\bin\javac.EXE
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 19.2.3
wanted: 19.2.3
react-native:
installed: 0.86.3
wanted: 0.86.3
react-native-windows: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Steps to reproduce
- Clone the reproducer branch, which is
mainat df32ce3 with one file added,src/__tests__/native/jest-helper-options.test.ts, and install:git clone --branch repro/jest-helper-option-types https://github.com/YevheniiKotyrlo/react-native-css cd react-native-css yarn install - Run
yarn test src/__tests__/native/jest-helper-options.test.ts.
src/__tests__/native/jest-helper-options.test.ts:
import { join } from "node:path";
import { compile } from "react-native-css/compiler";
import { registerCSS } from "react-native-css/jest";
import ts from "typescript";
const root = join(__dirname, "../../..").replaceAll("\\", "/");
const fixtureName = `${root}/src/__tests__/native/jest-helper-options.fixture.ts`;
function diagnostics(text: string): readonly string[] {
const { config } = ts.readConfigFile(`${root}/tsconfig.json`, (path) =>
ts.sys.readFile(path),
);
const { options } = ts.parseJsonConfigFileContent(config, ts.sys, root);
const host = ts.createCompilerHost(options, true);
const program = ts.createProgram([fixtureName], options, {
...host,
getCurrentDirectory: () => root,
fileExists: (name) => name === fixtureName || host.fileExists(name),
readFile: (name) => (name === fixtureName ? text : host.readFile(name)),
getSourceFile: (name, languageVersion, ...rest) =>
name === fixtureName
? ts.createSourceFile(name, text, languageVersion, true)
: host.getSourceFile(name, languageVersion, ...rest),
});
return ts
.getPreEmitDiagnostics(program, program.getSourceFile(fixtureName))
.map(({ messageText }) =>
ts.flattenDiagnosticMessageText(messageText, "\n"),
);
}
test('registerCSS takes the debug: "verbose" it hands compileWithAutoDebug', () => {
expect(
diagnostics(
[
`import { registerCSS } from "react-native-css/jest";`,
`registerCSS(".a { color: red; }", { debug: "verbose" });`,
].join("\n"),
),
).toStrictEqual([]);
});
test("registerCSS calls the logger it is given, as compile does", () => {
const css = ".a { color: red; }";
const compileMessages: string[] = [];
const registerMessages: string[] = [];
compile(css, {
logger: (message: string) => {
compileMessages.push(message);
},
});
registerCSS(css, {
logger: (message: string) => {
registerMessages.push(message);
},
});
expect(registerMessages).toStrictEqual(compileMessages);
});
Expected: both cases pass: debug: "verbose" type-checks, and registerCSS's logger receives the messages compile's does.
Actual: the type check reports Type 'string' is not assignable to type 'boolean | undefined'. for debug: "verbose", and registerCSS's logger receives none of the messages compile's receives.
The run's output on main at df32ce3, Windows 11, Node 26.12.1
FAIL src/__tests__/native/jest-helper-options.test.ts (30.993 s)
× registerCSS takes the debug: "verbose" it hands compileWithAutoDebug (2495 ms)
× registerCSS calls the logger it is given, as compile does (27 ms)
● registerCSS takes the debug: "verbose" it hands compileWithAutoDebug
expect(received).toStrictEqual(expected) // deep equality
- Expected - 1
+ Received + 3
- Array []
+ Array [
+ "Type 'string' is not assignable to type 'boolean | undefined'.",
+ ]
● registerCSS calls the logger it is given, as compile does
expect(received).toStrictEqual(expected) // deep equality
- Expected - 47
+ Received + 1
- Array [
- "Features {}",
- "Lightningcss first pass",
- ".a {
- "Lightningcss second pass",
- "Found 1 rules to process",
- "[
- "Exiting lightningcss",
- ]
+ Array []
Test Suites: 1 failed, 1 total
Tests: 2 failed, 2 total
Reproducible example repository
https://github.com/YevheniiKotyrlo/react-native-css/tree/repro/jest-helper-option-types
- 主要言語
- TypeScript
- スター
- 166
- フォーク
- 45
- 平均マージ
- 10日 1時間
- マージ済み PR(30日)
- 4
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
nativewind/react-native-css のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
nativewind/react-native-css#564 ·
メンテナーはふだん 5 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
nativewind/react-native-css#563 ·
メンテナーはふだん 5 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
nativewind/react-native-css#561 ·
メンテナーはふだん 5 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
nativewind/react-native-css#559 ·
メンテナーはふだん 5 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
nativewind/react-native-css#558 ·
メンテナーはふだん 5 日以内に返信
nativewind/react-native-css の issue をすべて見る
似ている issue
-
Cleanup Setup対応中かも @AlexanderKaran が今日担当しました。 オープンdocumentation enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
e18e/framework-tracker#769 ·
メンテナーはふだん 1 日以内に返信
-
bug v2
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
modelcontextprotocol/servers#5483 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 84/100
XiaomiMiMo/MiMo-Code#2783 ·
メンテナーはふだん 1 日以内に返信
-
area: web bug
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
kinqsradio/orbyn-engineering#227 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
joeldesante/TurfBuilder#258 ·
メンテナーはふだん 1 日以内に返信