chore(ci): upgrade built to ts7 rc #166
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,18 +15,18 @@ | |
| "@nvidia-elements/core": "workspace:*", | ||
| "@nvidia-elements/styles": "workspace:*", | ||
| "@nvidia-elements/themes": "workspace:*", | ||
| "vue": "3.5.39" | ||
| }, | ||
| "devDependencies": { | ||
| "@nvidia-elements/lint": "workspace:*", | ||
| "@tsconfig/node20": "20.1.9", | ||
| "@types/node": "catalog:", | ||
| "@vitejs/plugin-vue": "6.0.7", | ||
| "@vue/tsconfig": "0.9.1", | ||
| "eslint": "catalog:", | ||
| "typescript": "catalog:", | ||
| "vite": "catalog:", | ||
| "vue-tsc": "3.3.5" | ||
|
Comment on lines
27
to
+29
There was a problem hiding this comment. 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🌐 Web query:
💡 Result: As of June 30, 2026, there is no official documentation stating that vue-tsc 3.3.5 has verified support for TypeScript 7.0.1-rc [1][2]. vue-tsc acts as a wrapper around the TypeScript compiler (tsc) [3], and it typically maintains compatibility with the TypeScript versions supported by the underlying Vue Language Tools [3]. While vue-tsc allows users to point to a custom tsc path [1][4], it is not designed to guarantee support for unreleased or release candidate (rc) versions of TypeScript unless explicitly stated in the release notes or compatibility matrices for the specific version of the vue-tsc package. To check for compatibility, you can attempt to use the specific TypeScript version by installing it alongside vue-tsc and verifying that your type checking processes (e.g., vue-tsc --noEmit) complete without errors. Given that vue-tsc 3.3.5 was released on June 13, 2026 [1][2], you should review the official vuejs/language-tools GitHub repository releases for any updates regarding experimental support for newer TypeScript versions [5]. Citations:
🏁 Script executed: #!/bin/bash
set -euo pipefail
printf '\n== package files ==\n'
git ls-files 'projects/starters/vue/package.json' 'package.json' '**/catalog*' '**/typescript*' | sed -n '1,120p'
printf '\n== starter package.json ==\n'
cat -n projects/starters/vue/package.json
printf '\n== search for typescript-7 catalog ==\n'
rg -n '"typescript-7"|typescript-7|catalog:' -S . --glob '!**/node_modules/**' --glob '!**/dist/**' --glob '!**/build/**' | sed -n '1,200p'Repository: NVIDIA/elements Length of output: 14350 🏁 Script executed: #!/bin/bash
set -euo pipefail
python3 - <<'PY'
import json, urllib.request
for pkg, version in [('vue-tsc','3.3.5'), ('typescript','7.0.1-rc')]:
url = f'https://registry.npmjs.org/{pkg}/{version}'
try:
with urllib.request.urlopen(url, timeout=20) as r:
data = json.load(r)
print(f'== {pkg}@{version} ==')
for k in ['name','version','peerDependencies','dependencies','engines','keywords']:
if k in data:
print(k, data[k])
print()
except Exception as e:
print(f'FAILED {pkg}@{version}: {e}')
PYRepository: NVIDIA/elements Length of output: 471 🌐 Web query:
💡 Result: As of June 30, 2026, vue-tsc version 3.3.5 does not provide official support for TypeScript 7 (often referred to as TypeScript Native or tsgo) [1][2]. The current TypeScript 7 project is a public preview port of the TypeScript compiler to Go [1]. Because vue-tsc relies on patching the standard TypeScript (tsc) JavaScript implementation to integrate Vue-specific type checking, it is not currently compatible with the Go-based TypeScript architecture, which lacks the same internal plugin and patching mechanisms [1][3]. Additionally, vue-tsc continues to maintain its peerDependencies based on the standard Node.js-based TypeScript releases (typically requiring >= 5.0.0) [4]. There have been no announcements or documentation in the vue-tsc 3.3.5 release notes indicating integration with or support for TypeScript 7 [5][6]. Work regarding the potential implications of a non-JavaScript-based TypeScript implementation on Vue Language Tools is still in the early, speculative, or discussion phases [1][2][3]. Citations:
🏁 Script executed: #!/bin/bash
set -euo pipefail
python3 - <<'PY'
import json, urllib.request
url='https://registry.npmjs.org/vue-tsc/3.3.5'
with urllib.request.urlopen(url, timeout=20) as r:
data=json.load(r)
print(json.dumps({
'peerDependencies': data.get('peerDependencies'),
'dependencies': data.get('dependencies'),
'engines': data.get('engines'),
'version': data.get('version'),
}, indent=2))
PYRepository: NVIDIA/elements Length of output: 2747 Pin vue-tsc to a TypeScript 6-compatible release or keep 🤖 Prompt for AI Agents |
||
| }, | ||
| "wireit": { | ||
| "ci": { | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
pnpm minimumReleaseAgeExclude default minimumReleaseAge behavior💡 Result:
In pnpm,
minimumReleaseAgeExcludeis a configuration setting used to exempt specific dependencies from theminimumReleaseAgerestriction [1][2]. TheminimumReleaseAgesetting defines a "cooldown" period in minutes that must pass after a package version is published before pnpm will allow it to be installed [2][3]. As of pnpm v11, this defaults to 1440 minutes (1 day) to protect against supply chain attacks [4][5][6]. RegardingminimumReleaseAgeExclude: * Default Behavior: The default value isundefined[1]. When not configured, all dependencies must satisfy theminimumReleaseAgerequirement [1][3]. * Functionality: When you list packages underminimumReleaseAgeExclude, those packages are exempted from the release age restriction and can be installed immediately, regardless of how recently they were published [1][7]. * Configuration Options: You can exclude packages by name, using glob patterns (such as scopes like@myorg/*), or by pinning to specific versions (e.g.,webpack@4.47.0 || 5.102.1) [1][7]. If you setminimumReleaseAgeexplicitly in your configuration, pnpm automatically treatsminimumReleaseAgeStrictastrue(unless you manually set it tofalse), ensuring that if no version satisfies both the range and the age requirement, pnpm will not silently fall back to an immature version [8]. The built-in default of 1440 minutes remains non-strict for backward compatibility [8].Citations:
🏁 Script executed:
Repository: NVIDIA/elements
Length of output: 50371
🌐 Web query:
pnpm minimumReleaseAgeExclude alias dependency name npm alias underlying package name💡 Result:
In pnpm, when using the
minimumReleaseAgeExcludeconfiguration setting, the exclusion logic matches against the alias name used in your dependency definition, not the underlying package name [1][2]. If you have aliased a package—for instance, installingawesome-lodashaslodashviapnpm add lodash@npm:awesome-lodash—you must list the alias (lodash) in theminimumReleaseAgeExcludearray to exempt it from theminimumReleaseAgerestriction [1][3]. Key details regardingminimumReleaseAgeExcludebehavior: - Scope and Matching: The setting supports exact package names, glob patterns (e.g.,@myorg/*), and specific version pinning (e.g.,webpack@4.47.0 || 5.102.1) [1][4]. - Alias Handling: Becausepnpmresolves dependencies by alias, theminimumReleaseAgeExcludecheck is performed against the alias provided in thepackage.json[2]. - Usage: This feature is intended to allow specific dependencies to be installed immediately, bypassing the configuredminimumReleaseAge(which defaults to 1440 minutes in pnpm v11+) [1][4]. If you are using aliases to maintain multiple versions of the same package, you must ensure that the specific alias names used in your project are included in the exclusion list if you wish to bypass the maturity requirement for those specific instances [1][3].Citations:
Add
typescript-7tominimumReleaseAgeExclude. pnpm matches this list against the dependency alias, so the existingtypescriptentry does not exempttypescript-7; installs resolvingtypescript@7.0.1-rccan still be blocked by the age policy.🤖 Prompt for AI Agents