You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This update is being built upon some work I already did for NodeCG v2 usage but never merged into main. I will be targeting NodeCG v2.3.x which properly supports Node.js v22 (LTS) which means I can properly move to using "ES Modules" (ECMAScript) as the output on the extension builds.
Overhaul the tsconfig.json files and how they work.
Convert extension code to properly build.
Convert browser based code to properly build.
Remove module-alias/custom paths.
Add shared file for replicants in browser context.
Migrate to ESLint v9 and flat configs.
Add .vscode files.
extensions.json
Any other recommended extensions to add?
settings.json
Tweak file nesting patterns for ESLint v9.
Remove env.d.ts?
Remove nodecg-cli, don't install nodecg and suggest users install it globally (or add it as an optional dependency?)
Add/switch to Sass or SCSS.
Improve type file setup overall.
This includes ESLint related things.
Do we need a specific tsconfig.json setup?
Update README.md file.
Note why we use draft-07 JSON schema spec (VSCode).
Note (with a link) about additional Quasar configuration.
Any additional file comments that may be useful for future reference/other users.
The text was updated successfully, but these errors were encountered:
Things that I've changed but made a note of to verify I don't have issues with them in real world use-cases:
dashboard template having font-size: unset !important (which removes Quasar's 14px font-size setting, and seems to make it 16px); does this have any side effects with Quasar elements?
I have tweaked the Quasar primary colour to match that of the NodeCG primary colour, but need to test the rest of the colours.
This update is being built upon some work I already did for NodeCG v2 usage but never merged into main. I will be targeting NodeCG v2.3.x which properly supports Node.js v22 (LTS) which means I can properly move to using "ES Modules" (ECMAScript) as the output on the extension builds.
tsconfig.json
files and how they work.extension
code to properly build.module-alias
/custom paths..vscode
files.extensions.json
settings.json
env.d.ts
?nodecg-cli
, don't installnodecg
and suggest users install it globally (or add it as an optional dependency?)tsconfig.json
setup?README.md
file.draft-07
JSON schema spec (VSCode).The text was updated successfully, but these errors were encountered: