When @aws/lsp-codewhisperer is consumed as a module, we get this error at build time:
ERROR in ./node_modules/@aws/lsp-codewhisperer/out/language-server/chat/chatSessionService.js 16:34-74
Module not found: Error: Can't resolve '@amzn/codewhisperer-streaming' in '.../node_modules/@aws/lsp-codewhisperer/out/language-server/chat'
Even though @amzn/codewhisperer-streaming are packaged within the builds, build system is not able to resolve that path (e.g. not found in node_modules or aliases). Currently, our internal build system relies on manually releasing the streaming package, which is not possible for consumers.
Solution
To make it work for consumers, the most efficient way to solve this is to define a local dependency with a local path in package.json. During install command, package managers will detect the dependency and bring the package into node_modules. As a result, build systems (e.g. webpack, vite...) are able to resolve the module.
Testing
I tested in our internal release process.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Problem
When
@aws/lsp-codewhispereris consumed as a module, we get this error at build time:Even though
@amzn/codewhisperer-streamingare packaged within the builds, build system is not able to resolve that path (e.g. not found innode_modulesor aliases). Currently, our internal build system relies on manually releasing the streaming package, which is not possible for consumers.Solution
To make it work for consumers, the most efficient way to solve this is to define a local dependency with a local path in
package.json. During install command, package managers will detect the dependency and bring the package intonode_modules. As a result, build systems (e.g. webpack, vite...) are able to resolve the module.Testing
I tested in our internal release process.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.