brighterscript 0.65.17 → 0.65.19

package/CHANGELOG.md

@@ -6,6 +6,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 
 
+## [0.65.19](https://github.com/rokucommunity/brighterscript/compare/v0.65.18...v0.65.19) - 2024-01-30
+### Changed
+ - Backport v1 syntax changes ([#1034](https://github.com/rokucommunity/brighterscript/pull/1034))
+
+
+
+## [0.65.18](https://github.com/rokucommunity/brighterscript/compare/v0.65.17...v0.65.18) - 2024-01-25
+### Changed
+ - Refactor bsconfig documentation ([#1024](https://github.com/rokucommunity/brighterscript/pull/1024))
+ - Prevent overwriting `Program._manifest` if already set on startup ([#1027](https://github.com/rokucommunity/brighterscript/pull/1027))
+ - Improving null safety: Add FinalizedBsConfig and tweak plugin events ([#1000](https://github.com/rokucommunity/brighterscript/pull/1000))
+
+
+
 ## [0.65.17](https://github.com/rokucommunity/brighterscript/compare/v0.65.16...0.65.17) - 2024-01-16
 ### Changed
  - add documentation on pruneEmptyCodeFiles to the README ([#1012](https://github.com/rokucommunity/brighterscript/pull/1012))

package/README.md

@@ -14,7 +14,7 @@ A superset of Roku's BrightScript language. Compiles to standard BrightScript.
 The BrighterScript language provides new features and syntax enhancements to Roku's BrightScript language. Because the language is a superset of BrightScript, the parser and associated tools (VSCode integration, cli, etc...) work with standard BrightScript (.brs) files. This means you will get benefits (as described in the following section) from using the BrighterScript compiler, whether your project contains BrighterScript (.bs) files or not. The BrighterScript language transpiles to standard BrightScript, so your code is fully compatible with all roku devices.
 
 ## Features
-BrighterScript adds several new features to the BrightScript language such as Namespaces, classes, import statements, and more. Take a look at the language specification docs for more information.
+BrighterScript adds several new features to the BrightScript language such as namespaces, classes, import statements, and more. Take a look at the language specification docs for more information.
 
 [BrighterScript Language Specification](https://github.com/rokucommunity/BrighterScript/blob/master/docs/readme.md)
 
@@ -91,7 +91,6 @@ BrighterScript adds several new features to the BrightScript language such as Na
 </p>
 <br/>
 
-
 The BrighterScript project is used to power the popular [Brightscript Language](https://marketplace.visualstudio.com/items?itemName=rokucommunity.brightscript) VSCode extension, the [maestro framework](https://github.com/georgejecook/maestro/blob/master/docs/index.md), and more.
 
 [Contact us](https://github.com/rokucommunity/brighterscript/issues/new) if you use BrighterScript in your project and would like your logo listed above. More projects are adopting BrighterScript all the time, from using the new BrighterScript language features to simply using the compiler in their build pipeline.
@@ -163,434 +162,27 @@ If you need to configure `bsc`, you can do so in two ways:
 ## bsconfig.json
 
 ### Overview
-The presence of a `bsconfig.json` file in a directory indicates that the directory is the root of a BrightScript project. The `bsconfig.json` file specifies the root files and the compiler options required to compile the project.
-
-### Configuration inheritance with `extends`
-
-A `bsconfig.json` file can inherit configurations from another file using the `extends` property.
-
-The extends is a top-level property in `bsconfig.json`. `extends`’ value is a string containing a path to another configuration file to inherit from.
-
-The configuration from the base file are loaded first, then overridden by those in the inheriting config file. If a circularity is encountered, we report an error.
-
-The `files` property from the inheriting config file overwrite those from the base config file.
-
-All relative paths found in the configuration file will be resolved relative to the configuration file they originated in.
-
-### Optional `extends` and `project`
-There are situations where you want to store some compiler settings in a config file, but not fail if that config file doesn't exist. To do this, you can denote that your `extends` or `project` path is optional by prefixing it with a question mark (`?`). For example:
-
- - **bsconfig.json** `extends`
-    ```json
-    {
-      "extends": "?path/to/optional/bsconfig.json"
-    }
-    ```
- - CLI "extends"
-    ```
-    bsc --extends "?path/to/optional/bsconfig.json"
-    ```
-
- - CLI `project` argument
-    ```
-    bsc --project "?path/to/optional/bsconfig.json"
-    ```
- - Node.js API `extends`
-    ```
-    var programBuilder = new ProgramBuilder({
-        "extends": "?path/to/optional/bsconfig.json"
-    });
-    ```
- - Node.js API `project`
-    ```
-    var programBuilder = new ProgramBuilder({
-        "project": "?path/to/optional/bsconfig.json"
-    });
-    ```
-
-### `bsconfig.json` options
-
-These are the options available in the `bsconfig.json` file.
-
-#### `project`
-
-Type: `string`
-
-A path to a project file. This is really only passed in from the command line or the NodeJS API, and should not be present in `bsconfig.json` files. Prefix with a question mark (?) to prevent throwing an exception when the file does not exist.
-
-#### `extends`
-
-Type: `string`
-
-Relative or absolute path to another `bsconfig.json` file that this `bsconfig.json` file should import and then override. Prefix with a question mark (?) to prevent throwing an exception when the file does not exist. Defaults to `undefined`.
-
-Note: child config properties completely replace parent config properties. For example: if a parent and child bsconfigs both specify an array for `plugins`, or `files`, or `diagnosticFilters`, etc., then the parent's setting will be completely ignored and the child's setting will be used instead.
-
-#### `cwd`
-
-Type: `string`
-
-If present, overrides the current working directory when invoking `bsc`. Defaults to `process.cwd()`.
-
-#### `rootDir`
-
-Type: `string`
-
-The root directory of your roku project. Defaults to `process.cwd()`.
-
-#### `stagingDir`
-
-Type: `string`
-
-The folder where the transpiled files are placed. This folder will be created automatically if it does not exist, and will be deleted after transpilation completes unless `retainStagingDir` is set to `true`. Defaults to `./out/.roku-deploy-staging`.
-
-#### `retainStagingDir`
-
-Type: `boolean`
-
-Prevent the staging folder from being deleted after creating the package. Defaults to `false`, meaning that the folder is deleted every time.
-
-#### `removeParameterTypes`
-
-Type: `boolean`
-
-If true, removes the explicit type to function's parameters and return (i.e. the `as type` syntax); otherwise keep this information.
-
-#### `files`
-
-Type:
-```typescript
-Array<
-  string |
-  string[] |
-  {
-    src: string | string[],
-    dest: string
-  }>
-```
-
-The files array is how you specify what files are included in your project. Any strings found in the files array must be relative to rootDir, and are used as include filters, meaning that if a file matches the pattern, it is included.
-
-For most standard projects, the default files array should work just fine:
-
-```jsonc
-{
-    "files": [
-        "source/**/*",
-        "components/**/*",
-        "images/**/*",
-        "manifest"
-    ]
-}
-```
-
-This will copy all files from the standard roku folders directly into the package while maintaining each file's relative file path within rootDir.
-
-If you want to include additional files, you will need to provide the entire array. For example, if you have a folder with other assets, you could do the following:
-
-```jsonc
-{
-    "files": [
-        "source/**/*",
-        "components/**/*",
-        "images/**/*",
-        "manifest"
-        //your folder with other assets
-        "assets/**/*",
-    ]
-}
-```
-
-If a `bsconfig.json` file specifies a parent config using the `extends` field, and the child specifies a `files` field, then the parent's `files` field will be completely overridden by the child.
-
-##### Excluding files
-
-You can exclude files from the output by prefixing your file patterns with "!". This is useful in cases where you want everything in a folder EXCEPT certain files.
-
-```jsonc
-{
-    "files": [
-        "source/**/*",
-        "!source/some/unwanted/file.brs"
-    ]
-}
-```
-
-The files array is processed from top to bottom, with later patterns overriding previous ones. This means that in order to exclude a file which is included by another pattern, the negative pattern using `!` must occur **after** the positive pattern.
-
-##### File pattern resolution
-
-All patterns will be resolved relative to rootDir, with their relative positions within rootDir maintained.
-
-Patterns may not reference files outside of `rootDir` unless the `{ src, dest }` form is used (see below). For example:
-
-```jsonc
-{
-    "rootDir": "C:/projects/CatVideoPlayer",
-    "files": [
-        "source/main.brs",
-
-        //NOT allowed because it navigates outside the rootDir
-        "../common/promise.brs"
-    ]
-}
-```
-
-Any valid glob pattern is supported. For more information, see the documentation on the underlying [fast-glob](https://github.com/mrmlnc/fast-glob) library.
-
-Empty folders are not copied.
-
-Paths to folders will be ignored. If you want to copy a folder and its contents, use the glob syntax (i.e. `some_folder/**/*`).
-
-##### Specifying file destinations
-
-For more advanced use cases, you may provide an object which contains the source pattern and output path. This allows you to be very specific about what files to copy, and where they are placed in the output folder. This option also supports copying files from outside the `rootDir`.
-
-The object structure is as follows:
-
-```typescript
-{
-    /**
-     * A glob pattern string or file path, or an array of glob pattern strings and/or file paths.
-     * These can be relative paths or absolute paths.
-     * All non-absolute paths are resolved relative to the rootDir
-     */
-    src: Array<string | string[]>;
-    /**
-     * The relative path to the location in the output folder where the files should be placed,
-     * relative to the root of the output folder
-     */
-    dest: string | undefined
-}
-```
-
-If `src` is a non-glob path to a single file, then `dest` should include the filename and extension. For example:
-
-```jsonc
-{ "src": "lib/Promise/promise.brs", "dest": "source/promise.brs" }
-```
-
-If `src` is a glob pattern, then dest should be a path to the folder in the output directory. For example:
-
-```jsonc
-{ "src": "lib/*.brs", "dest": "source/lib" }
-```
-
-If `src` is a path to a folder, it will be ignored. If you want to copy a folder and its contents, use the glob syntax. The following example will copy all files from the lib/vendor folder recursively:
-
-```jsonc
-{ "src": "lib/vendor/**/*", "dest": "vendor" }
-```
-
-If `dest` is not specified it will default to the root of the output folder.
-
-An example of combining regular and advanced file patterns:
-
-```jsonc
-{
-    "rootDir": "C:/projects/CatVideoPlayer",
-    "files": [
-        "source/main.brs",
-        {
-          "src": "../common/promise.brs",
-          "dest": "source/common"
-        }
-    ]
-}
-```
-
-##### File collision handling
-
-Because file entries are processed in order you can override a file by specifying an alternative later in the files array.
-
-For example, if you have a base project and a child project that wants to override specific files, you could do the following:
+The presence of a `bsconfig.json` file in a directory indicates that the directory is the root of a BrightScript project. The `bsconfig.json` file specifies the root files and the compiler options required to compile the project. Here is a minimal example, which is recommended for new projects:
 
 ```jsonc
 {
+    "rootDir": "src",
     "files": [
-        {
-            //copy all files from the base project
-            "src": "../BaseProject/**/*"
-        },
-        // Override "../BaseProject/themes/theme.brs"
-        // with "${rootDir}/themes/theme.brs"
-        "themes/theme.brs"
-    ]
+        "**/*"
+    ],
+    "stagingFolderPath": "dist",
+    "retainStagingFolder": true,
+    //this flag tells BrighterScript that for every xml file, try to import a .bs file with the same name and location
+    "autoImportComponentScript": true,
+    "sourceMap": true
 }
 ```
 
-#### `outFile`
-
-Type: `string`
-
-The path (including filename) where the output file should be placed. Defaults to `"./out/${WORKSPACE_FOLDER_NAME}.zip"`.
-
-#### `createPackage`
-
-Type: `boolean`
-
-Causes the build to create a zip package. Defaults to `true`. This setting is ignored when `deploy` is enabled.
-
-#### `watch`
-
-Type: `boolean`
-
-If `true`, the server will keep running and will watch and recompile on every file change. Defaults to `false`.
-
-#### `deploy`
-
-Type: `boolean`
-
-If `true`, after a successful build, the project will be deployed to the Roku specified in host. Defaults to `false`. If this field is set to `true`, then the `host` and `password` fields must be set as well.
-
-#### `host`
-
-Type: `string`
-
-The host of the Roku that this project will deploy to when the `deploy` field is set to `true`. Defaults to `undefined`.
-
-#### `username`
-
-Type: `string`
-
-The username that will be used to deploy to the Roku device when the `deploy` field is set to `true`. Defaults to `undefined`.
-
-#### `password`
-
-Type: `string`
-
-The password that will be used to deploy to the Roku device when the `deploy` field is set to `true`. Defaults to `undefined`.
-
-#### `emitFullPaths`
-
-Type: `boolean`
-
-Emit full paths to files when printing diagnostics to the console. Defaults to `false`.
-
-#### `emitDefinitions`
-
-Type: `boolean`
-
-Emit type definition files (`d.bs`) during transpile. Defaults to `false`.
-
-#### `diagnosticFilters`
-
-Type: `Array<string | number | {src: string; codes: number[]}`
-
-A list of filters used to hide diagnostics.
-   - A `string` value should be a relative-to-root-dir or absolute file path or glob pattern of the files that should be excluded. Any file matching this pattern will have all diagnostics supressed.
-   - A `number` value should be a diagnostic code. This will supress all diagnostics with that code for the whole project.
-   - An object can also be provided to filter specific diagnostic codes for a file pattern. For example,
-
-        ```jsonc
-        "diagnosticFilters": [{
-            "src": "vendor/**/*",
-            "codes": [1000, 1011] //ignore these specific codes from vendor libraries
-        }]
-        ```
-
-Defaults to `undefined`.
-
-If a child bsconfig extends from a parent bsconfig, and both bsconfigs specify `diagnosticFilters`, the parent bsconfig's `diagnosticFilters` field will be completely overwritten.
-
-#### `diagnosticSeverityOverrides`
-
-Type: `Record<string | number, 'hint' | 'info' | 'warn' | 'error'>`
-
-A map of error codes and severity levels that will override diagnostics' severity. When a diagnostic generator doesn't offer enough control on an error's severity, this is a tool to work around blocking errors, or raise the level of other errors.
-
-      ```jsonc
-      "diagnosticSeverityOverrides": {
-        "1011": "error",       //raise a warning to an error
-        "LINT1001": "warn" //oops we have lots of those to fix... later
-      }
-      ```
-
-#### `diagnosticLevel`
-
-Type: `"hint" | "info" | "warn" | "error"`
-
-Specify what diagnostic levels are printed to the console. This has no effect on what diagnostics are reported in the LanguageServer. Defaults to `"warn"`.
-
-#### `autoImportComponentScript`
-
-Type: `bool`
-
-BrighterScript only: will automatically import a script at transpile-time for a component with the same name if it exists. Defaults to `false`.
-
-#### `sourceRoot`
-
-Type: `string`
-
-Override the root directory path where debugger should locate the source files. The location will be embedded in the source map to help debuggers locate the original source files. This only applies to files found within `rootDir`. This is useful when you want to preprocess files before passing them to BrighterScript, and want a debugger to open the original files. This option also affects the `SOURCE_FILE_PATH` and `SOURCE_LOCATION` source literals.
-
-#### `plugins`
-
-Type: `Array<string>`
-
-List of node scripts or npm modules to load as plugins to the BrighterScript compiler. Defaults to `undefined`.
-
-If a child bsconfig extends from a parent bsconfig, and both bsconfigs specify a `plugins` field, the child's `plugins` field will completely overwrite the parent's `plugins` field.
-
-#### `require`
-
-Type: `Array<string>`
-
-List of node scripts or npm modules to load during the startup sequence. Useful for running things like `ts-node/require`. Defaults to `undefined`.
-
-If a child bsconfig extends from a parent bsconfig, and both bsconfigs specify a `require` field, the child's `require` field will completely overwrite the parent's `require` field.
-
-#### `allowBrighterScriptInBrightScript`
-
-Type: `boolean`
-
-Allow BrighterScript features (classes, interfaces, etc...) to be included in BrightScript (`.brs`) files, and force those files to be transpiled.
-
-#### `bslibDestinationDir`
-
-Type: `string`
-
-Override the destination directory for the bslib.brs file.  Use this if you want
-to customize where the bslib.brs file is located in the staging directory.  Note
-that using a location outside of `source` will break scripts inside `source`
-that depend on bslib.brs.  Defaults to `source`.
-
-#### `pruneEmptyCodeFiles`
-
-Type: `boolean`
-
-Remove files from the final package which would be empty or consist entirely of comments after compilation. Also removes imports of any such empty scripts from XML files. This can speed up sideloading packages during development. Defaults to `false`.
-
-
-## Ignore errors and warnings on a per-line basis
-In addition to disabling an entire class of errors in `bsconfig.json` by using `ignoreErrorCodes`, you may also disable errors for a subset of the complier rules within a file with the following comment flags:
- - `bs:disable-next-line`
- - `bs:disable-next-line: code1 code2 code3`
- - `bs:disable-line`
- - `bs:disable-line: code1 code2 code3`
-
-Here are some examples:
-
-```BrightScript
-sub Main()
-    'disable errors about invalid syntax here
-    'bs:disable-next-line
-    DoSomething(
-
-    DoSomething( 'bs:disable-line
-
-    'disable errors about wrong parameter count
-    DoSomething(1,2,3) 'bs:disable-line
-
-    DoSomething(1,2,3) 'bs:disable-line:1002
-end sub
-
-sub DoSomething()
-end sub
-```
+More information on the config file format may be found in the [bsconfig.json documentation](https://github.com/rokucommunity/BrighterScript/blob/master/docs/bsconfig.md).
 
-The primary motivation for this feature was to provide a stopgap measure to hide incorrectly-thrown errors on legitimate BrightScript code due to parser bugs. This is still a new project and it is likely to be missing support for certain BrightScript syntaxes. It is recommended that you only use these comments when absolutely necessary.
+## Suppressing compiler messages
 
+The BrighterScript compiler emits errors and warnings when it encounters potentially invalid code. Errors and warnings may also be emitted by compiler plugins, such as by [the BrighterScript linter](https://github.com/rokucommunity/bslint). These messages can be suppressed if needed; see [the documentation](https://github.com/rokucommunity/BrighterScript/blob/master/docs/suppressing-compiler-messages.md).
 
 ## ropm support
 In order for BrighterScript-transpiled projects to work as ropm modules, they need a reference to [bslib](https://github.com/rokucommunity/bslib/blob/master/source/bslib.brs) (the BrightScript runtime library for BrighterScript features) in their package. As `ropm` and `brighterscript` become more popular, this could result in many duplicate copies of `bslib.brs`.

package/dist/BsConfig.d.ts

@@ -187,3 +187,6 @@ export interface BsConfig {
      */
     bslibDestinationDir?: string;
 }
+declare type OptionalBsConfigFields = '_ancestors' | 'sourceRoot' | 'project' | 'manifest' | 'noProject' | 'extends' | 'host' | 'password' | 'require' | 'stagingFolderPath' | 'diagnosticLevel' | 'rootDir' | 'stagingDir';
+export declare type FinalizedBsConfig = Omit<Required<BsConfig>, OptionalBsConfigFields> & Pick<BsConfig, OptionalBsConfigFields>;
+export {};

package/dist/PluginInterface.d.ts

@@ -1,6 +1,8 @@
 import type { CompilerPlugin } from './interfaces';
 import type { Logger } from './Logger';
-export declare type Arguments<T> = [T] extends [(...args: infer U) => any] ? U : [T] extends [void] ? [] : [T];
+export declare type PluginEventArgs<T> = {
+    [K in keyof Required<T> as Required<T>[K] extends (...args: any[]) => any ? K : never]: Required<T>[K] extends (...args: any[]) => any ? Parameters<Required<T>[K]> : never;
+};
 export default class PluginInterface<T extends CompilerPlugin = CompilerPlugin> {
     private plugins;
     /**
@@ -19,7 +21,7 @@ export default class PluginInterface<T extends CompilerPlugin = CompilerPlugin>
     /**
      * Call `event` on plugins
      */
-    emit<K extends keyof T & string>(event: K, ...args: Arguments<T[K]>): void;
+    emit<K extends keyof PluginEventArgs<T> & string>(event: K, ...args: PluginEventArgs<T>[K]): void;
     /**
      * Add a plugin to the beginning of the list of plugins
      */

package/dist/PluginInterface.js.map

@@ -1 +1 @@
-{"version":3,"file":"PluginInterface.js","sourceRoot":"","sources":["../src/PluginInterface.ts"],"names":[],"mappings":";;AAEA,qCAAoC;AAOpC,MAAqB,eAAe;IAgBhC,YACY,OAAyB,EACjC,OAGU;QAJF,YAAO,GAAP,OAAO,CAAkB;QAMjC,IAAI,CAAA,OAAO,aAAP,OAAO,uBAAP,OAAO,CAAE,WAAW,CAAC,IAAI,MAAK,QAAQ,EAAE;YACxC,IAAI,CAAC,MAAM,GAAG,OAA4B,CAAC;SAC9C;aAAM;YACH,IAAI,CAAC,MAAM,GAAI,OAAe,aAAf,OAAO,uBAAP,OAAO,CAAU,MAAM,CAAC;YACvC,IAAI,CAAC,cAAc,GAAG,CAAC,OAAe,aAAf,OAAO,uBAAP,OAAO,CAAU,cAAc,MAAK,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC;SACnF;IACL,CAAC;IASD;;OAEG;IACI,IAAI,CAA6B,KAAQ,EAAE,GAAG,IAAqB;QACtE,KAAK,IAAI,MAAM,IAAI,IAAI,CAAC,OAAO,EAAE;YAC7B,IAAK,MAAc,CAAC,KAAK,CAAC,EAAE;gBACxB,IAAI;oBACA,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,iBAAQ,CAAC,KAAK,EAAE,CAAC,MAAM,CAAC,IAAI,EAAE,KAAK,CAAC,EAAE,GAAG,EAAE;wBACvD,MAAc,CAAC,KAAK,CAAC,CAAC,GAAG,IAAI,CAAC,CAAC;oBACpC,CAAC,CAAC,CAAC;iBACN;gBAAC,OAAO,GAAG,EAAE;oBACV,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,6BAA6B,MAAM,CAAC,IAAI,IAAI,KAAK,GAAG,EAAE,GAAG,CAAC,CAAC;oBAC7E,IAAI,CAAC,IAAI,CAAC,cAAc,EAAE;wBACtB,MAAM,GAAG,CAAC;qBACb;iBACJ;aACJ;SACJ;IACL,CAAC;IAED;;OAEG;IACI,QAAQ,CAA4C,MAAS;QAChE,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE;YACnB,IAAI,CAAC,OAAO,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;SAChC;QACD,OAAO,MAAM,CAAC;IAClB,CAAC;IAED;;OAEG;IACI,GAAG,CAA4C,MAAS;QAC3D,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE;YACnB,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;SAC7B;QACD,OAAO,MAAM,CAAC;IAClB,CAAC;IAEM,GAAG,CAAC,MAAsB;QAC7B,OAAO,IAAI,CAAC,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC;IACzC,CAAC;IAEM,MAAM,CAA4C,MAAS;QAC9D,IAAI,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE;YAClB,IAAI,CAAC,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC;SACrD;QACD,OAAO,MAAM,CAAC;IAClB,CAAC;IAED;;OAEG;IACI,KAAK;QACR,IAAI,CAAC,OAAO,GAAG,EAAE,CAAC;IACtB,CAAC;CACJ;AA/FD,kCA+FC"}
+{"version":3,"file":"PluginInterface.js","sourceRoot":"","sources":["../src/PluginInterface.ts"],"names":[],"mappings":";;AAEA,qCAAoC;AAuBpC,MAAqB,eAAe;IAgBhC,YACY,OAAyB,EACjC,OAGU;QAJF,YAAO,GAAP,OAAO,CAAkB;QAMjC,IAAI,CAAA,OAAO,aAAP,OAAO,uBAAP,OAAO,CAAE,WAAW,CAAC,IAAI,MAAK,QAAQ,EAAE;YACxC,IAAI,CAAC,MAAM,GAAG,OAA4B,CAAC;SAC9C;aAAM;YACH,IAAI,CAAC,MAAM,GAAI,OAAe,aAAf,OAAO,uBAAP,OAAO,CAAU,MAAM,CAAC;YACvC,IAAI,CAAC,cAAc,GAAG,CAAC,OAAe,aAAf,OAAO,uBAAP,OAAO,CAAU,cAAc,MAAK,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC;SACnF;IACL,CAAC;IASD;;OAEG;IACI,IAAI,CAA8C,KAAQ,EAAE,GAAG,IAA2B;QAC7F,KAAK,IAAI,MAAM,IAAI,IAAI,CAAC,OAAO,EAAE;YAC7B,IAAK,MAAc,CAAC,KAAK,CAAC,EAAE;gBACxB,IAAI;oBACA,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,iBAAQ,CAAC,KAAK,EAAE,CAAC,MAAM,CAAC,IAAI,EAAE,KAAK,CAAC,EAAE,GAAG,EAAE;wBACvD,MAAc,CAAC,KAAK,CAAC,CAAC,GAAG,IAAI,CAAC,CAAC;oBACpC,CAAC,CAAC,CAAC;iBACN;gBAAC,OAAO,GAAG,EAAE;oBACV,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,6BAA6B,MAAM,CAAC,IAAI,IAAI,KAAK,GAAG,EAAE,GAAG,CAAC,CAAC;oBAC7E,IAAI,CAAC,IAAI,CAAC,cAAc,EAAE;wBACtB,MAAM,GAAG,CAAC;qBACb;iBACJ;aACJ;SACJ;IACL,CAAC;IAED;;OAEG;IACI,QAAQ,CAA4C,MAAS;QAChE,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE;YACnB,IAAI,CAAC,OAAO,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;SAChC;QACD,OAAO,MAAM,CAAC;IAClB,CAAC;IAED;;OAEG;IACI,GAAG,CAA4C,MAAS;QAC3D,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE;YACnB,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;SAC7B;QACD,OAAO,MAAM,CAAC;IAClB,CAAC;IAEM,GAAG,CAAC,MAAsB;QAC7B,OAAO,IAAI,CAAC,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC;IACzC,CAAC;IAEM,MAAM,CAA4C,MAAS;QAC9D,IAAI,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE;YAClB,IAAI,CAAC,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC;SACrD;QACD,OAAO,MAAM,CAAC;IAClB,CAAC;IAED;;OAEG;IACI,KAAK;QACR,IAAI,CAAC,OAAO,GAAG,EAAE,CAAC;IACtB,CAAC;CACJ;AA/FD,kCA+FC"}

package/dist/Program.d.ts

@@ -1,5 +1,5 @@
 import type { CodeAction, CompletionItem, Position, Range, SignatureInformation, Location } from 'vscode-languageserver';
-import type { BsConfig } from './BsConfig';
+import type { BsConfig, FinalizedBsConfig } from './BsConfig';
 import { Scope } from './Scope';
 import { BrsFile } from './files/BrsFile';
 import { XmlFile } from './files/XmlFile';
@@ -29,15 +29,12 @@ export interface SignatureInfoObj {
     signature: SignatureInformation;
 }
 export declare class Program {
-    /**
-     * The root directory for this program
-     */
-    options: BsConfig;
     constructor(
     /**
      * The root directory for this program
      */
     options: BsConfig, logger?: Logger, plugins?: PluginInterface);
+    options: FinalizedBsConfig;
     logger: Logger;
     private createGlobalScope;
     /**
@@ -124,7 +121,7 @@ export declare class Program {
     /**
      * roku filesystem is case INsensitive, so find the scope by key case insensitive
      */
-    getScopeByName(scopeName: string): Scope;
+    getScopeByName(scopeName: string): Scope | undefined;
     /**
      * Return all scopes
      */
@@ -317,8 +314,9 @@ export declare class Program {
     /**
      * Try to find and load the manifest into memory
      * @param manifestFileObj A pointer to a potential manifest file object found during loading
+     * @param replaceIfAlreadyLoaded should we overwrite the internal `_manifest` if it already exists
      */
-    loadManifest(manifestFileObj?: FileObj): void;
+    loadManifest(manifestFileObj?: FileObj, replaceIfAlreadyLoaded?: boolean): void;
     /**
      * Get a map of the manifest information
      */

package/dist/Program.js

@@ -35,7 +35,6 @@ class Program {
      * The root directory for this program
      */
     options, logger, plugins) {
-        this.options = options;
         /**
          * A graph of all files and their dependencies.
          * For example:
@@ -45,6 +44,11 @@ class Program {
         this.dependencyGraph = new DependencyGraph_1.DependencyGraph();
         this.diagnosticFilterer = new DiagnosticFilterer_1.DiagnosticFilterer();
         this.diagnosticAdjuster = new DiagnosticSeverityAdjuster_1.DiagnosticSeverityAdjuster();
+        /**
+         * A scope that contains all built-in global functions.
+         * All scopes should directly or indirectly inherit from this scope
+         */
+        this.globalScope = undefined;
         /**
          * A set of diagnostics. This does not include any of the scope diagnostics.
          * Should only be set from `this.validate()`
@@ -614,14 +618,12 @@ class Program {
      * @param file the file
      */
     getScopesForFile(file) {
-        if (typeof file === 'string') {
-            file = this.getFile(file);
-        }
+        const resolvedFile = typeof file === 'string' ? this.getFile(file) : file;
         let result = [];
-        if (file) {
+        if (resolvedFile) {
             for (let key in this.scopes) {
                 let scope = this.scopes[key];
-                if (scope.hasFile(file)) {
+                if (scope.hasFile(resolvedFile)) {
                     result.push(scope);
                 }
             }
@@ -1149,8 +1151,13 @@ class Program {
     /**
      * Try to find and load the manifest into memory
      * @param manifestFileObj A pointer to a potential manifest file object found during loading
+     * @param replaceIfAlreadyLoaded should we overwrite the internal `_manifest` if it already exists
      */
-    loadManifest(manifestFileObj) {
+    loadManifest(manifestFileObj, replaceIfAlreadyLoaded = true) {
+        //if we already have a manifest instance, and should not replace...then don't replace
+        if (!replaceIfAlreadyLoaded && this._manifest) {
+            return;
+        }
         let manifestPath = manifestFileObj
             ? manifestFileObj.src
             : path.join(this.options.rootDir, 'manifest');