القائمة
'three-globe' v2.x changed atmosphere/globe configuration from method chaining to property setters — `.atmosphereDayIncrement is not a function` at runtime
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Find and fix WCAG 2.2 accessibility issues. Two modes — report (sweep a codebase or page, produce a prioritized written report, no edits) and fix (audit→edit→verify loop on a target). Prefers direct-CDP live-DOM auditing; falls back to HTML-string audits.
Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch. Reports only new violations introduced, violations fixed, and pre-existing count. Use `scan` for a full audit with no diffing.
Audit a live page for accessibility issues and locate each violation precisely — pass a URL, a config target name (e.g. `accesslint:scan dev`), or nothing to use the default target from accesslint.config.json. Ensures a debuggable Chrome, runs the @accesslint/core engine via CDP, and returns a worklist of live-DOM WCAG violations grounded to each violation's DOM selector and source file:line. Locates; doesn't edit — output drives fixes by Claude. Use it for "is this page accessible", or to verify a UI change. For diffing against uncommitted changes or a branch, use the `diff` skill.
Diagnose when AI features silently return 'Offline' or 'no API key' despite valid settings
Remove native title bar double-rendering in Electron by setting `frame: false` and using CSS `-webkit-app-region` for window dragging
When a utility exports a boolean constant but a component imports and calls it as a function — `isNative()` instead of `isNative` — causes "is not a function" at render time
استنادا إلى تصنيف SOC المهني
| name | three-globe-v2-breaking-api-change |
| description | 'three-globe' v2.x changed atmosphere/globe configuration from method chaining to property setters — `.atmosphereDayIncrement is not a function` at runtime |
three-globe v2.x (published around 2025) changed how globe properties are configured. The old v1 API used fluent method chaining; v2 uses property setters on the instance.
Old v1 code that fails silently or crashes:
globe = new ThreeGlobe()
.showAtmosphere(true) // ❌ v2: returns undefined, chain breaks
.atmosphereColor('#3b82f6') // ❌ TypeError on undefined
.atmosphereDayIncrement(0.1) // ❌ "is not a function"
The error message is: TypeError: (intermediate value).showAtmosphere(...).atmosphereColor(...).atmosphereDayIncrement is not a function
globe = new ThreeGlobe()
globe.showAtmosphere = true
globe.atmosphereColor = '#14fbfb'
// atmosphereDayIncrement is removed in v2 — atmosphere altitude is implicit
Wrap atmosphere configuration in try/catch so the globe still renders even if the API shifts again:
try {
globe.showAtmosphere = true
globe.atmosphereColor = '#14fbfb'
} catch (e) {
// atmosphere is cosmetic — globe renders fine without it
}
The three-globe package has gone through breaking changes between major versions. Projects that were built with v1.x will crash at runtime after a dependency update or fresh install pulls v2.x. The npm registry always serves the latest compatible version unless pinned, so npm install in a new environment will get v2. The error appears in the browser console (renderer) or Electron main process at component mount time.
new ThreeGlobe() calls:
grep -r "\.showAtmosphere\|\.atmosphereColor\|\.atmosphereDayIncrement" src/
npx vite build to verify