[chrisdp]

Brings v1 up to date with master through 0.73.8 (0.73.5 – 0.73.8).

Ported from master

• Fix "Maximum call stack size exceeded" when transpiling very large classes and blocks (Fix "Maximum call stack size exceeded" when transpiling very large classes and blocks #1937). This also converts the v1-only places with the same pattern to util.pushAll: the conditional compile #else/#else if bodies, select case (case bodies and the final assembly), the class builder's member assignments, and #if member handling inside classes. Each of these has a new regression test in Statement.spec.ts, and all four new tests (counting the namespaced-class test inherited from master) crashed on v1 before the change.
• Allow a namespaced const to reference an outer symbol with the same name (Allow a namespaced const to reference an outer symbol with the same name #1905, Add component-scope coverage for recursive const resolution #1904). Ported into Scope.getConstFileLink (both the cached and the map lookup paths), ScopeValidator, and BrsFileTranspileProcessor, which replaced master's BrsFilePreTranspileProcessor on v1. The deleted file's new tests moved to BrsFileTranspileProcessor.spec.ts.
• bsc --init (Add bsc --init to create a new bsconfig.json #1892), with a template rewritten for v1's bsconfig (see below).
• Fix crash stripping a sourceMappingURL comment from non-transpiled files (Fix crash stripping sourceMappingURL comment from non-transpiled files #1821).
• Add the ... (DotDotDot) lexer tests (Add ... (DotDotDot) token to the lexer #1896). v1 already had the token.
• Worker-thread test timeouts raised to 120s for slow macOS runners (chore: bump worker thread test timeouts for slow macOS runners #1908).
• Nightly security-audit schedule (chore: Run nightly security audit at 1am Eastern #1872), and follow-redirects bumped to 1.16.1 so npm run audit passes.

Kept from v1

• CHANGELOG.md, the version, and the package.json overrides, including v1's narrowly scoped uuid overrides (same reasoning as Merge master into v1 #1814).
• benchmarks/package.json: v8-profiler-next stays removed on v1, because it no longer builds on current Node. That also makes master's benchmark node-gyp/tar overrides unnecessary: neither package is in v1's benchmarks dependency tree.
• Master's Add ... (DotDotDot) token to the lexer #1896 parser tests assert that ... is rejected, but v1 supports spread (Add spread operator support #1839), so v1's parser tests win.

Worth a reviewer's attention

• Type-system change for Allow a namespaced const to reference an outer symbol with the same name #1905. Porting the resolver alone wasn't enough on v1. namespace promises: const chain = chain with a global chain() still transpiled to promises_chain, because v1's type system resolved the initializer to the const itself. util.getSelfNamedConstOfInitializer now detects a reference to the same name inside the initializer of a namespaced const. VariableExpression.getType then resolves that reference from the file-level table, and VariableExpression.transpile no longer namespace-qualifies it. This matches master's rule: skip the namespaced match and use the global name.
• Pre-existing v1 bug fixed: wrong symbol in transpiled output. With a global foo() and namespace ns: const foo = 1, a print foo inside ns transpiled on v1 to print foo. On a device that is the global function, not the namespace const; master emits print 1. The cause was util.isVariableShadowingSomething, which treated the namespace const as shadowed whenever any file-level symbol shared its name. It now stops once the name resolves to the namespace's own member. Its only caller is the const/enum inliner. Two regression tests were added for this.
• bsc --init template for v1. Master's template writes options that v1 deprecates (stagingDir, deploy, copyToStaging, createPackage, top-level compiler options) and some it doesn't have (host, password, username, outFile, retainStagingDir). The v1 template keeps master's recommended defaults: "outDir": "dist", plus minFirmwareVersion, autoImportComponentScript, sourceMap and relativeSourceMaps under compilerOptions. It keeps master's descriptions for every option that still exists on v1. The test now also checks that the generated config produces no deprecation diagnostics.
• Adapted ported tests. Master's new const tests called testTranspile without await, which lint rejects on v1 because testTranspile is async there. Adding await is what exposed the type-system gap above. The six Allow a namespaced const to reference an outer symbol with the same name #1905 circular-reference tests use expectDiagnosticsIncludes, because v1 also reports cycles during type resolution, with duplicate and partial chains and a "Cannot find name" in one case. I compared those diagnostics on a clean v1 build and they are identical, so this is existing v1 behaviour, not something the port changed. circularReferenceDetected calls drop v0's scope-name argument, and two Fix crash stripping sourceMappingURL comment from non-transpiled files #1821 tests needed setFile<BrsFile>/setFile<XmlFile> for v1's types.

Verification: npm run test:nocover: 5407 passing, 0 failing. npx tsc --noEmit, npm run lint and npm run audit are clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_011mEYuXEbLYduJAVzNw1Ldi