Pooya Parsa
Pooya Parsa
Hi. Do you mind to open a PR for fix?
As i undrestand correctly, they essentially provide docker image for Node? What would be benefit of supporting this project as a preset? (update, i see [this example](https://github.com/open-runtimes/open-runtimes/tree/main/runtimes/node-21.0) it is docker+node+micro...
Okay thanks for the context. BTW i plan to open source a similar solution for js servers but it is way lighter than what seems they do and better tailored...
Moving to unified tracker #2973
Thanks for reporting. Ill look into it. For context nitro main branch is going under heavy refactors to prepare for v3 so more issues like this are likely to happen...
Hi dear @cyperdark. Bundling `.node` dependencies is not supported yet. You are welcome to contribute and add support (it should be via rollup plugins)
This issue is on track and I might have some ideas to support it in a nonbreaking change version with slight behavior-only changes. In the meantime, please consider issue 👍🏼...
Sadly, it is not that straightforward without behavior changes / overhead because not all nitro presets are compatible with an async entry today but thanks for your feedback dear @robertpatrick.
Generally, we should support ignore patterns for public directory (https://github.com/unjs/nitro/issues/843) PR is welcome to add a hotfix to ignore this specific file from copying in public assets plugin.
Thanks for PR ❤️ I think this needs to be more thorough thinking before exposing from nitro runtime utils. Diverging `env` definition one more level and allowing to complete override...