You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A dependency on the get-function-location library exists in @nestia/core > WebSocketAdaptor. However, that library is not specified in the package.json of @nestia/core, which is causing an error "Can not find module get-function-location" in the runtime environment.
I solved the problem by temporarily installing get-function-location into the project. The library is installed by @nestia/sdk, so if I had the @nestia/sdk library installed in the runtime environment, I would not have found this bug. However, @nestia/sdk is a documentation build tool and is suitable for devDependencies, which are deleted with the npm prune --omit=dev command.
In conclusion, you should explicitly require a dependency on get-function-location in the @nestia/core library.
@nestia/core ^3.1.3
@nestia/sdk ^3.1.3
The text was updated successfully, but these errors were encountered:
Bug Report
A dependency on the get-function-location library exists in
@nestia/core
>WebSocketAdaptor
. However, that library is not specified in the package.json of@nestia/core
, which is causing an error "Can not find moduleget-function-location
" in the runtime environment.I solved the problem by temporarily installing
get-function-location
into the project. The library is installed by@nestia/sdk
, so if I had the@nestia/sdk
library installed in the runtime environment, I would not have found this bug. However,@nestia/sdk
is a documentation build tool and is suitable for devDependencies, which are deleted with thenpm prune --omit=dev
command.In conclusion, you should explicitly require a dependency on
get-function-location
in the@nestia/core
library.@nestia/core ^3.1.3
@nestia/sdk ^3.1.3
The text was updated successfully, but these errors were encountered: