Editor extension for NativeCore: Go to Definition and Go to References between ref="name" and this.name.
This package lives in the NativeCoreJS monorepo. It is not published to npm with the runtime; install it as a VS Code / Cursor extension (VSIX or local link). Marketplace ID (when published): NativeCoreJS.vscode-nativecore-refs.
What it does
Cursor on
Go to Definition (F12)
Go to References (Shift+F12)
ref="step2El" in HTML or component template
this.step2El / assertRefs('step2El') in the paired controller or same component
All attr + member + assert usages
this.step2El in JS/TS
Matching ref="step2El" in the paired view or same file
Open packages/vscode-nativecore-refs (or the monorepo root)
Press F5 (launch config opens an Extension Development Host)
In a NativeCore app, put the caret on a ref="..." value and press F12
Link into Cursor / VS Code
$src = "C:\Users\DavidToledo\Documents\Personal\nativecorejs\packages\vscode-nativecore-refs"
$ext = "$env:USERPROFILE\.cursor\extensions\NativeCoreJS.vscode-nativecore-refs-0.1.0"
# For VS Code: $env:USERPROFILE\.vscode\extensions\...
New-Item -ItemType Junction -Path $ext -Target $src -Force
Reload the window after linking.
Package a VSIX
npm run package -w nativecore-refs
Then: Extensions → Install from VSIX…
Settings
nativecoreRefs.enabled (default true)
nativecoreRefs.requireConfig (default false) — only run when nativecore.config.json is in the workspace
Limits (MVP)
No Rename Symbol yet
Dynamic / string-built HTML refs are not discovered until they appear as source text
Common names like titleEl may still match multiple files; pairing prefers the route-linked controller
Scaffolded apps
create-nativecore recommends this extension via .vscode/extensions.json. Until it is on the Marketplace, install from this package (link or VSIX) as above.