Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36715
53625484 cleanup(testing): expose createOrEditViteConfig via internal and unblock node vitest fixture ## Current Behavior createOrEditViteConfig exported from @nx/vitest/generators without an API contract. New CNW prompt spec from master still expects node to exclude vitest. ## Expected Behavior Helper moves to @nx/vitest/internal (first-party surface). Node stack fixture no longer expects an exclusion. ## Related Issue(s) NXC-4780
by Jack Hsu
Failed
36715
Generating fix→
89e50959 fix(testing): address js specs, baseUrl mappings, and emission edge cases ## Current Behavior --js apps leave the generated spec outside typed projects (no allowJs). Root tsconfig paths with a non-root baseUrl map to the wrong directory. CR/LF in emitted literals breaks the config. resolveAlias leaks an unused join import into existing configs. ## Expected Behavior allowJs set in tsconfig.spec.json for --js apps. Root path mappings resolve against baseUrl. Line terminators escaped. join import only emitted for new config files. ## Related Issue(s) NXC-4780
by Jack Hsu
Failed
36715
f814c680 fix(testing): harden generated vitest config emission and legacy alias support ## Current Behavior Legacy workspaces cannot resolve root tsconfig aliases in next vitest specs. Generated specs/ sits outside tsconfig.spec.json include in ts-solution setups. testInclude backslashes and alias apostrophes can corrupt emitted configs; URL .pathname percent-encodes spaces. resolveAlias silently dropped for existing configs. ## Expected Behavior Root tsconfig paths mirrored as offset aliases in non-ts-solution workspaces (wildcard and exact entries). tsconfig.spec.json include covers specs/. Literals fully escaped (backslash + quote); aliases emitted via join(import.meta.dirname, ...). Existing-config path warns when resolveAlias cannot be applied. ## Related Issue(s) NXC-4780
by Jack Hsu
Succeeded
36715
3e3628ed fix(testing): resolve the nextjs alias in generated vitest configs ## Current Behavior A spec importing via the @/* alias fails to resolve under vitest: the alias lives in the app tsconfig.json, tsconfig.spec.json extends tsconfig.base.json without it, and neither vite-tsconfig-paths nor vite 8's native resolve.tsconfigPaths applies on vitest's transform path. ## Expected Behavior Generated config mirrors the app tsconfig paths as explicit resolve.alias entries (new resolveAlias option on @nx/vitest createOrEditViteConfig); tsconfig.spec.json gets the paths copied for typechecking. testInclude values escape single quotes. e2e app test imports via @/ to prove it. Assertion-narrating comments dropped. ## Related Issue(s) NXC-4780
by Jack Hsu
Succeeded
36715
3e3628ed fix(testing): resolve the nextjs alias in generated vitest configs ## Current Behavior A spec importing via the @/* alias fails to resolve under vitest: the alias lives in the app tsconfig.json, tsconfig.spec.json extends tsconfig.base.json without it, and neither vite-tsconfig-paths nor vite 8's native resolve.tsconfigPaths applies on vitest's transform path. ## Expected Behavior Generated config mirrors the app tsconfig paths as explicit resolve.alias entries (new resolveAlias option on @nx/vitest createOrEditViteConfig); tsconfig.spec.json gets the paths copied for typechecking. testInclude values escape single quotes. e2e app test imports via @/ to prove it. Assertion-narrating comments dropped. ## Related Issue(s) NXC-4780
by Jack Hsu
Failed
36715
Generating fix→
88ddaf6b fix(testing): cover no-src layouts in next vitest include and pin colocated spec in e2e ## Current Behavior Vitest include misses colocated specs in root app/ or pages/ when --no-src is used. The e2e colocated-spec assertion passes even if colocation regresses. ## Expected Behavior Include covers {src,app,pages,specs}. e2e asserts both spec files actually ran. ## Related Issue(s) NXC-4780
by Jack Hsu
Canceled
36715
88ddaf6b fix(testing): cover no-src layouts in next vitest include and pin colocated spec in e2e ## Current Behavior Vitest include misses colocated specs in root app/ or pages/ when --no-src is used. The e2e colocated-spec assertion passes even if colocation regresses. ## Expected Behavior Include covers {src,app,pages,specs}. e2e asserts both spec files actually ran. ## Related Issue(s) NXC-4780
by Jack Hsu
Succeeded
36715
6a4eba72 cleanup(testing): move vitest config helper changes out of @nx/vite for next apps ## Current Behavior Next vitest wiring goes through @nx/vite createOrEditViteConfig, and the generated config pulls in the deprecated nxViteTsPaths/nxCopyAssetsPlugin helpers (plus an @nx/vite dep). ## Expected Behavior @nx/vitest exports its own createOrEditViteConfig (testInclude added there, @nx/vite untouched). Next configs skip the deprecated helper plugins via skipNxPlugins, so no @nx/vite dep is generated or needed. ## Related Issue(s) NXC-4780
by Jack Hsu
Succeeded
36715
6a4eba72 cleanup(testing): move vitest config helper changes out of @nx/vite for next apps ## Current Behavior Next vitest wiring goes through @nx/vite createOrEditViteConfig, and the generated config pulls in the deprecated nxViteTsPaths/nxCopyAssetsPlugin helpers (plus an @nx/vite dep). ## Expected Behavior @nx/vitest exports its own createOrEditViteConfig (testInclude added there, @nx/vite untouched). Next configs skip the deprecated helper plugins via skipNxPlugins, so no @nx/vite dep is generated or needed. ## Related Issue(s) NXC-4780
by Jack Hsu
Succeeded
36715
315a47b2 fix(testing): install missing runtime dep and colocated specs for next vitest apps ## Current Behavior Generated vitest.config.mts imports @nx/vite/plugins/* but @nx/vite never lands in the user's package.json (skipViteConfig bypasses the generator that adds it), so nx test fails at config load in non-ts-solution workspaces. Specs colocated under src/ are silently skipped. ## Expected Behavior @nx/vite added as devDependency when the config references it. Vitest include covers {src,specs}. ## Related Issue(s) NXC-4780
by Jack Hsu
Failed
36715
23d68add feat(testing): offer vitest consistently across generators with a unitTestRunner option ## Current Behavior - @nx/next:application only allows jest/none while @nx/next:library allows vitest - @nx/react host/remote/federate-module schema enums block vitest even though the underlying application generator supports it - create-nx-workspace hides the vitest choice for Next.js presets and the node stack, though node/express/nest generators accept it ## Expected Behavior - @nx/next:application accepts --unitTestRunner=vitest (standalone vitest.config.mts, specs/ include, spec types in tsconfig.json) - @nx/react host/remote/federate-module accept vitest and pass it through - create-nx-workspace prompts include vitest for Next.js and node stacks; react-native/expo still exclude it (jest-only upstream) - @nx/vite createOrEditViteConfig accepts testInclude for projects whose specs live outside src/ ## Related Issue(s) Fixes NXC-4780
by Jack Hsu