-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
feat: decouple nitro inference engine into a library #1635
Comments
@louis-jan can help on prioritize this one, my suggestion is just to commit directly to nitro repo, i think no need seperate repo |
- Require node engine - Pin working node and yarn versions for use with Volta - Add workflow to check build manually for forked repos
- Require node engine - Add node-gyp as required on some platforms - Pin working node and yarn versions for use with Volta - Add workflow to check build manually for forked repos
- Require node engine - Add node-gyp as required on some platforms - Pin working node and yarn versions for use with Volta - Add workflow to check build manually for forked repos
- Require node engine - Add node-gyp as required on some platforms - Pin working node and yarn versions for use with Volta - Add workflow to check build manually for forked repos
- Require node engine - Add node-gyp as required on some platforms - Pin working node and yarn versions for use with Volta - Add workflow to check build manually for forked repos - Add make target to run github action build dev locally
- Require node engine - Add node-gyp as required on some platforms - Pin working node and yarn versions for use with Volta - Add workflow to check build manually for forked repos - Add make target to run github action build dev locally
Second on this, I'm about to make a Raycast front-end UI for nitro, so I prefer to have official node wrapper to be available on NPM, then I can add it as a dependency directly in my project. 🤓 |
hi @InNoobWeTrust i appreciate the raycast front-end |
…nference-engine-into-a-library [menloresearch/jan#1635] feat: decouple nitro engine into a library
Thanks, @InNoobWeTrust. I'm going to close this issue, and we will open new issues if needed for bug fixes or improvements. |
Problem
Right now the way to manage nitro process is directly inside nitro extension, it's very bad for devex and also hard to keep track, debug
Success Criteria
Decoupled out into a seperate library so that user can just fix nitro library rather than entire extension
The text was updated successfully, but these errors were encountered: