How to use source map of esbuild with SEA #97
Unanswered
louis222220
asked this question in
Q&A
Replies: 1 comment
-
There is currently no VFS/FS hooks support in Node.js in general. Effectively the SEA supports a main script and a list of assets, and it's up to the user how they can map the bundled assets and redirect fs calls (internal or user-land) to it (currently, they can only monkey-patch fs, until proper fs hooks are agreed upon and implemented by someone : #43). Internally, not being able to locate the file inside the SEA (as there's no VFS support) would just lead to missing source maps. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have build an application with esbuild and Node SEA. The application works.
However, after I build with source-map option of esbuild. The final application is just as the same, instead of logging with source-map.
The following is my script in Dockerfile:
My directory:
It works fine if I keep the file
app-out.cjs
in the directory. But the functionality of source-map disappears if I delete the bundled source file.The condition conflict with my purpose because I want to delivery only the application without source code.
Could anyone give me some idea or advice?
Beta Was this translation helpful? Give feedback.
All reactions