N
Nuxt8h ago
negative

Nitro error when using vscode-languagedetection (worker init error)

Hey, Im using this package to detect code language in a string. This package uses machine learning (tensorflow) to work and its working fine when I use it in a Vue component executing it on server (wrapping it up with import.meta.server condition), but when I try to use it in the server/api folder, Nitro crash and it does not tell anything. I also tried to make a Nuxt plugin and a Nitro plugin but same error.
No description
6 Replies
kapa.ai
kapa.ai8h ago
Hi @negative. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on the information provided in the knowledge sources, I don't have specific details about the vscode-languagedetection package or its compatibility with Nitro. However, I can provide some general insights about Nitro and server-side code in Nuxt that might be relevant to your issue. The error you're experiencing when trying to use the vscode-languagedetection package in the server/api folder is likely related to limitations in the Nitro server environment. Nitro, which is the server engine used by Nuxt, has certain restrictions on what can be imported and used in the server runtime. Here are a few points to consider: 1. Server Runtime Limitations: As mentioned in the Nuxt documentation on app config limitations (https://nuxt.com/docs/guide/directory-structure/app-config#known-limitations), some auto-imports and Vue-related functionalities are not available in the Nitro context. This could potentially affect packages that rely on browser-specific or Vue-specific features. 2. Import Restrictions: The error message you're seeing might be similar to what's described in this GitHub issue: Latest Nuxt Update Fails with Bun Package Manager (https://github.com/nuxt/nuxt/issues/29884). The error suggests that certain modules cannot be imported in the server runtime. 3. Machine Learning Dependencies: Since the vscode-languagedetection package uses TensorFlow, which is a complex library with potential system dependencies, it might not be compatible with the more restricted server environment of Nitro. To troubleshoot this issue, you could try the following: 1. Check if the package has any specific instructions for server-side usage in Node.js environments. 2. Try wrapping the package usage in a try-catch block to see if you can capture more detailed error information. 3. Consider using the package only on the client-side if possible, or look for alternative packages that are known to work in server-side Node.js environments. 4. If you need to use this specific package on the server, you might need to create a separate Node.js service outside of your Nuxt application to handle the language detection functionality. Unfortunately, without more specific error messages or details about how Nitro is crashing, it's difficult to provide a more precise solution. If you can capture any error logs or stack traces, that would be helpful for further debugging. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai8h ago
<@158354252312477697> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
negative
negativeOP7h ago
try and catch does not help because the error is when the worker init. Removing the line that executes the runModel method fix the error, but of course I want to fix it not to hide the error. I actually don't know how to debug this error to understand what is happening, dev server errors need to be improved (https://github.com/nitrojs/nitro/issues/2927)
negative
negativeOP7h ago
In a Vue component works fine in the server side
No description
negative
negativeOP7h ago
Got more info while creating the repro
No description
negative
negativeOP6h ago
Already tried and the error occurs in the “new ModelOperations()”, and as mentioned before the try and catch does not work, its like the code crashes when importing modules not when executing that code But on a Vue component works fine, the same code
Want results from more Discord servers?
Add your server