Neither local project nor glitch deployment work in Blender

Hello, I started a new Needle Project in Blender, but when I want to start the preview server, I get an error message saying the vite.js module cannot be found. I’m on Needle Engine 3.51.4 with Node 20.9.0

Also, when I try to deploy the project to glitch, Glitch only shows me the template sandbox scene, but not my scene.

Hello Dylan! Let’s address your issue step by step.

Regarding the Vite.js Module Not Found Error

  1. Ensure Vite is Installed: It seems the project may be missing the Vite dependency. Run the following command in your terminal within the project directory:
    npm install vite
    
  2. Check package.json: Ensure that your package.json includes Vite as a dependency. If it’s not there, you can add it manually:
    {
      "dependencies": {
        "vite": "latest",
        // other dependencies
      }
    }
    

For the Glitch Deployment Issue

  1. Project Structure: Make sure that your scene is properly referenced in the project structure. Check if your main scene file is being picked up in the Glitch project settings.
  2. Glitch Logs: Inspect the logs in Glitch to check if there are any error messages related to loading your scene. This can provide clues if there’s an issue in the deployment process.
  3. Assets Path: Ensure that all assets used in your scene are correctly linked and accessible in the Glitch environment.

Additional Suggestions

  • Make sure to use the correct version of Node.js as compatible with Needle Engine.
  • If you’re still encountering issues, please check if there are any error logs available and share those.

Feel free to ask if you need further assistance on any of these steps!

1 replies left - Get a PRO license for more AI replies.
thread_0sxkF4Rl0bEgv3WhghKPt4cU
Reply to this message to continue the conversation

So, I ran npm install vite, and got these error messages:

npm WARN deprecated npmlog@5.0.1: This package is no longer supported.
npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated are-we-there-yet@2.0.0: This package is no longer supported.
npm WARN deprecated gauge@3.0.2: This package is no longer supported.

up to date, audited 512 packages in 5s

61 packages are looking for funding
run npm fund for details

18 vulnerabilities (13 moderate, 2 high, 3 critical)

To address issues that do not require attention, run:
npm audit fix

Some issues need review, and may require choosing
a different dependency.

Hello Dylan! It looks like you encountered some warnings and vulnerabilities while installing Vite. Here’s how you can handle this:

Handling Deprecated Warnings

  1. Ignore Deprecated Warnings: The warnings about deprecated packages generally do not affect the functionality of your project immediately. However, it’s good practice to keep your dependencies up-to-date. Consider updating those packages in the future.

Addressing Vulnerabilities

  1. Run Audit Fix: You can attempt to fix the vulnerabilities by running:

    npm audit fix
    

    This command will automatically fix any vulnerabilities that can be resolved without breaking changes.

  2. Review Manual Fixes: After running the above, you should check for vulnerabilities that need manual intervention. You can do this with:

    npm audit
    

    Review the output and decide if specific packages can be updated or replaced.

Next Steps

  • After resolving the warnings and vulnerabilities, try starting your Needle project again with:
    npm run dev
    
  • Verify if the Vite error persists.

Let me know how it goes or if you encounter any new errors!

0 replies left - Get a PRO license for more AI replies.
thread_0sxkF4Rl0bEgv3WhghKPt4cU
Reply to this message to continue the conversation

Running npm audit or audit fix gives me this list of issues, but doesn’t resolve anything. Running npm start again still brings up the missing vine.js error.

npm audit report

got <11.8.5
Severity: moderate
Got allows a redirect to a UNIX socket - Got allows a redirect to a UNIX socket · CVE-2022-33987 · GitHub Advisory Database · GitHub
No fix available
node_modules/got
package-json <=6.5.0
Depends on vulnerable versions of got
node_modules/package-json
latest-version 0.2.0 - 5.1.0
Depends on vulnerable versions of package-json
node_modules/latest-version
update-notifier 0.2.0 - 5.1.0
Depends on vulnerable versions of latest-version
node_modules/update-notifier
msdf-bmfont-xml >=2.6.0
Depends on vulnerable versions of update-notifier
node_modules/msdf-bmfont-xml
@needle-tools/helper *
Depends on vulnerable versions of msdf-bmfont-xml
Depends on vulnerable versions of request
node_modules/@needle-tools/helper

jpeg-js <=0.4.3
Severity: high
Infinite loop in jpeg-js - Infinite loop in jpeg-js · CVE-2022-25851 · GitHub Advisory Database · GitHub
Uncontrolled resource consumption in jpeg-js - Uncontrolled resource consumption in jpeg-js · CVE-2020-8175 · GitHub Advisory Database · GitHub
fix available via npm audit fix
node_modules/jpeg-js
@jimp/jpeg <=0.12.0
Depends on vulnerable versions of jpeg-js
node_modules/@jimp/jpeg
@jimp/types <=0.11.1-canary.891.908.0
Depends on vulnerable versions of @jimp/jpeg
node_modules/@jimp/types
jimp 0.3.6-alpha.5 - 0.21.4–canary.1163.d07ed6254d130e2995d24101e93427ec091016e6.0
Depends on vulnerable versions of @jimp/custom
Depends on vulnerable versions of @jimp/types
node_modules/jimp

minimist <=0.2.3
Severity: critical
Prototype Pollution in minimist - Prototype Pollution in minimist · CVE-2020-7598 · GitHub Advisory Database · GitHub
Prototype Pollution in minimist - Prototype Pollution in minimist · CVE-2021-44906 · GitHub Advisory Database · GitHub
fix available via npm audit fix
node_modules/mkdirp/node_modules/minimist
mkdirp 0.4.1 - 0.5.1
Depends on vulnerable versions of minimist
node_modules/mkdirp
@jimp/core <=0.21.4–canary.1163.d07ed6254d130e2995d24101e93427ec091016e6.0
Depends on vulnerable versions of mkdirp
Depends on vulnerable versions of phin
node_modules/@jimp/core
@jimp/custom <=0.21.4–canary.1163.d07ed6254d130e2995d24101e93427ec091016e6.0
Depends on vulnerable versions of @jimp/core
node_modules/@jimp/custom

phin <3.7.1
Severity: moderate
phin may include sensitive headers in subsequent requests after redirect - phin may include sensitive headers in subsequent requests after redirect · GHSA-x565-32qp-m3vf · GitHub Advisory Database · GitHub
fix available via npm audit fix
node_modules/phin

request *
Severity: moderate
Server-Side Request Forgery in Request - Server-Side Request Forgery in Request · CVE-2023-28155 · GitHub Advisory Database · GitHub
Depends on vulnerable versions of tough-cookie
No fix available
node_modules/request

tough-cookie <4.1.3
Severity: moderate
tough-cookie Prototype Pollution vulnerability - tough-cookie Prototype Pollution vulnerability · CVE-2023-26136 · GitHub Advisory Database · GitHub
No fix available
node_modules/tough-cookie

vite <=4.5.5
Severity: high
Vite dev server option server.fs.deny can be bypassed when hosted on case-insensitive filesystem - Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystem · CVE-2024-23331 · GitHub Advisory Database · GitHub
Vite’s server.fs.deny did not deny requests for patterns with directories. - Vite's `server.fs.deny` did not deny requests for patterns with directories. · CVE-2024-31207 · GitHub Advisory Database · GitHub
Vite DOM Clobbering gadget found in vite bundled scripts that leads to XSS - Vite DOM Clobbering gadget found in vite bundled scripts that leads to XSS · CVE-2024-45812 · GitHub Advisory Database · GitHub
Vite’s server.fs.deny is bypassed when using ?import&raw - Vite's `server.fs.deny` is bypassed when using `?import&raw` · CVE-2024-45811 · GitHub Advisory Database · GitHub
Websites were able to send any requests to the development server and read the response in vite - Websites were able to send any requests to the development server and read the response in vite · CVE-2025-24010 · GitHub Advisory Database · GitHub
fix available via npm audit fix
node_modules/vite

18 vulnerabilities (13 moderate, 2 high, 3 critical)

To address issues that do not require attention, run:
npm audit fix

Some issues need review, and may require choosing
a different dependency.

Hi DylanKay, I’m sorry but I can’t help you right now. You have reached the maximum number of replies. :brain:. Please try again later or get a PRO license for more AI help.
**

Okay, so the solution was in fact really simple: My project path was just too long. I placed the Needle Project two levels higher up in the hierarchy and now everything works fine =)

1 Like

Hi DylanKay, I’m sorry but I can’t help you right now. You have reached the maximum number of replies. :brain:. Please try again later or get a PRO license for more AI help.
**

It’s often the case in Blender with long path issues ^^’

Currently file paths in Blender have a max of 160 chars, and file names 80 chars

This topic was automatically closed 13 days after the last reply. New replies are no longer allowed.