What happens
Deploying a TypeScript Function whose entrypoint imports ./modular-procurement-shared.ts completed the entrypoint upload but the runtime build failed because the imported local file was not included. I expected deploy to bundle or upload the local dependency graph, or fail locally with a clear unsupported-import message.
Command
insforge functions deploy <slug> --file functions/<entry>.ts
Expected
A deployable Function source can use local shared modules, or the CLI documents and validates that only a single self-contained file is supported.
Workaround
Bundled each entrypoint and its local imports into a temporary single file with esbuild, then deployed that bundle while keeping modular source in the repository.
Triage finding
Verified on HEAD and in the published 0.2.8 tarball that functions deploy still does a bare readFileSync of the single --file entrypoint with no bundling, no dependency-graph upload, and no local validation of relative imports — README documents neither constraint, and no existing issue/PR tracks it; cheapest first step is a fail-fast pre-flight check for .//../ imports rather than letting it fail in the server-side build.
· win32 10.0.26200
Filed automatically from user feedback.
What happens
Deploying a TypeScript Function whose entrypoint imports ./modular-procurement-shared.ts completed the entrypoint upload but the runtime build failed because the imported local file was not included. I expected deploy to bundle or upload the local dependency graph, or fail locally with a clear unsupported-import message.
Command
Expected
A deployable Function source can use local shared modules, or the CLI documents and validates that only a single self-contained file is supported.
Workaround
Bundled each entrypoint and its local imports into a temporary single file with esbuild, then deployed that bundle while keeping modular source in the repository.
Triage finding
Verified on HEAD and in the published 0.2.8 tarball that
functions deploystill does a barereadFileSyncof the single--fileentrypoint with no bundling, no dependency-graph upload, and no local validation of relative imports — README documents neither constraint, and no existing issue/PR tracks it; cheapest first step is a fail-fast pre-flight check for.//../imports rather than letting it fail in the server-side build.· win32 10.0.26200
Filed automatically from user feedback.