BeyondJS Doesn't Recognize tsconfig.json After Initial Error

[jircdev]

Description:
When creating a module in the BeyondJS project and failing to include a tsconfig.json file, BeyondJS appropriately throws an error regarding the missing configuration file. However, if a tsconfig.json file is subsequently added, BeyondJS fails to recognize the file, even after restarting the service. This issue arises due to the caching of the initial error, requiring manual deletion of the .beyond folder (cache) to prompt BeyondJS to recognize the newly added tsconfig.json file.

Steps to Reproduce:

1. Create a module without a tsconfig.json file in a BeyondJS project.
2. Observe the error thrown by BeyondJS regarding the missing configuration file.
3. Add a tsconfig.json file to the module.
4. Restart the BeyondJS service.
5. Notice that BeyondJS still fails to recognize the tsconfig.json file and doesn't resolve the initial error.
6. Manually delete the .beyond folder (cache).
7. Upon restarting the service again, BeyondJS correctly recognizes the tsconfig.json file and resolves the issue.

Expected Behavior:
BeyondJS should automatically recognize the presence of a tsconfig.json file in a module and resolve any related errors after the file is added, without requiring manual deletion of the .beyond folder.

Additional Notes:

• It would be beneficial to investigate and address the caching behavior causing BeyondJS to persistently hold onto the initial error state, even after a tsconfig.json file is provided.
• Consider implementing a mechanism to ensure that BeyondJS updates its internal state and error cache when configuration files are added or modified, thereby avoiding the need for manual intervention.

Environment:

• BeyondJS version: 1.2.0-beta.2

• Operating System: Windows 10.