Error importing `config` bundle in package.

[jircdev]

Description

When importing the config submodule from the main package, which is automatically generated by BeyondJS, the import is successful in bundles of type "widget" but fails in bundles of type "code". This behavior is unexpected and suggests an issue with how BeyondJS handles automatic submodule imports in different bundle contexts.

Context

• Module in Question: package-name/config
• Bundle Types: "widget" (working), "code" (failing)
• Error Message: Cannot find module 'package-name/config'
• BeyondJS Version: 1.2.0-beta.config.dts.0

The problem arises when attempting to use the config submodule within a 'code' type bundle, which is part of the same package and is intended to be used as an application.

Expected Behavior

All submodules generated by BeyondJS should be resolvable and importable across all bundle types without errors.

Actual Behavior

Importing the config submodule within a 'code' type bundle results in a module resolution error, whereas no such error occurs in a 'widget' type bundle.

Steps to Reproduce

1. Create a 'widget' type bundle and import package config files. Observe successful import.
2. Create a 'code' type bundle and attempt the same import.
3. Import the code component from the 'widget'. Observe the module resolution error.