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
I've been using this great package with Heroku and I tried to bundle my Node.js app with TypeScript using esbuild. However, I encountered a bug that said Error The input directory "/app/bin" does not exist..
I already fixed that error by adding to my build script the flag --packages=external (didn't know that was recommended by the esbuild documentation). Therefore, this is the build script that I have that works with this package:
I'm wondering if it's possible to add a clarification in the documentation in case some else encounters this same bug. The only issue that I can think of is that I'm not entirely sure if the problem that I had was exclusively to Heroku or not. So probably some research needs to be done with at least a couple of different services to check if the problem persists.
If you think this makes any sense, I'm willing to research about it and, if the same problem is anywhere else, I can create PR with the clarification.
Let me know if this makes any sense.
Why would it be useful?
It will help the people who will use esbuild to bundle their Node.js app.
The text was updated successfully, but these errors were encountered:
What would you like to have implemented?
Hello there!
I've been using this great package with Heroku and I tried to bundle my Node.js app with TypeScript using esbuild. However, I encountered a bug that said
Error The input directory "/app/bin" does not exist.
.I already fixed that error by adding to my build script the flag
--packages=external
(didn't know that was recommended by the esbuild documentation). Therefore, this is the build script that I have that works with this package:I'm wondering if it's possible to add a clarification in the documentation in case some else encounters this same bug. The only issue that I can think of is that I'm not entirely sure if the problem that I had was exclusively to Heroku or not. So probably some research needs to be done with at least a couple of different services to check if the problem persists.
If you think this makes any sense, I'm willing to research about it and, if the same problem is anywhere else, I can create PR with the clarification.
Let me know if this makes any sense.
Why would it be useful?
It will help the people who will use esbuild to bundle their Node.js app.
The text was updated successfully, but these errors were encountered: