-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESM module loader fails on TypeScript projects #143
Comments
lance
added a commit
to lance/faas-js-runtime
that referenced
this issue
Dec 15, 2022
This resolves issues where function source may be in a subdirectory, for example `./build` in a TypeScript project. Fixes: nodeshift#143 Signed-off-by: Lance Ball <lball@redhat.com>
lance
added a commit
to lance/faas-js-runtime
that referenced
this issue
Dec 16, 2022
This resolves issues where function source may be in a subdirectory, for example `./build` in a TypeScript project. Fixes: nodeshift#143 Signed-off-by: Lance Ball <lball@redhat.com>
lance
added a commit
to lance/faas-js-runtime
that referenced
this issue
Dec 16, 2022
This resolves issues where function source may be in a subdirectory, for example `./build` in a TypeScript project. Fixes: nodeshift#143 Signed-off-by: Lance Ball <lball@redhat.com>
lance
added a commit
to lance/faas-js-runtime
that referenced
this issue
Dec 16, 2022
This resolves issues where function source may be in a subdirectory, for example `./build` in a TypeScript project. Fixes: nodeshift#143 Signed-off-by: Lance Ball <lball@redhat.com>
lance
added a commit
that referenced
this issue
Jan 5, 2023
This resolves issues where function source may be in a subdirectory, for example `./build` in a TypeScript project. Fixes: #143 Signed-off-by: Lance Ball <lball@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The module loader is looking for a
package.json
file in the directory where the function was found. In the case of TypeScript functions, the function itself will be in./build
and thepackage.json
file is in../
. I think the loader should probably traverse up directories until it finds apackage.json
file before it fails.See: knative/func#1468 (comment)
/cc @lholmquist
The text was updated successfully, but these errors were encountered: