Unable to install MapEditor dependencies

[islaiter]

Hello team!

Been trying to install MapEditor to do a few changes, while trying to install dependencies, I get the following warns:

 WARN  deprecated @types/jszip@3.4.1: This is a stub types definition. jszip provides its own type definitions, so you do not need this installed.
 WARN  deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
 WARN  deprecated vue@2.6.14: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
 WARN  11 deprecated subdependencies found: @humanwhocodes/config-array@0.13.0, @humanwhocodes/object-schema@2.0.3, acorn-import-assertions@1.9.0, consolidate@0.15.1, core-js@2.6.12, glob@7.2.3, inflight@1.0.6, popper.js@1.16.1, rimraf@3.0.2, stable@0.1.8, webpack-chain@6.5.1

If I try to ignore those and just build from there, I get the error:

node is not recognized as an internal or external command

Also tried to install latest Node version, v22.14.0 using chocolatey

choco install nodejs-lts

And setting up corepack for pnpm

corepack enable pnpm

After that, trying to build again, gives the following error:

Vue packages version mismatch:

• vue@2.6.14 (..\Documents\Battlefield 3\Server\Admin\Mods\mapeditor\WebUI\node_modules.pnpm\vue@2.6.14\node_modules\vue\dist\vue.runtime.common.js)
• vue-template-compiler@2.7.16 (..\Battlefield 3\Server\Admin\Mods\mapeditor\WebUI\node_modules.pnpm\vue-template-compiler@2.7.16\node_modules\vue-template-compiler\package.json)

Hey mate, It looks like there's a compatibility issue between your vue and vue-template-compiler packages. They need to be at matching versions to work properly together. If they're not, it can lead to problems in your Vue.js application. You should check both packages if you can, and make sure they are updated to the same version. 1. Check your current version,s of vue and vue-template-compiler. using the following command: npm list vue vue-template-compiler if there is a version mismatch, resolve the version mismatch, you generally want to ensure that both packages are of the same major and minor version. For example you can do this by runnin npm install vue@2.6.14 vue-template-compiler@2.6.14 --save If there are still issues after those steps, you can consider performing a clean installation of your node modules directory ,but let me know first if its working for you ;) Cheers, MadDog

[islaiter]

Hello MadDogRM! Thank for the help first of all.

It seems like some progress has been made thanks to your commands, managed to solve the conflict issues with vue and vue-compiler-package by using the command you provided, now everything installs correctly, but I still can't build as I'm getting the following error:

Error: spawn ..\Documents\Battlefield 3\Server\Admin\Mods\mapeditor\WebUI\node_modules.pnpm\vextpack@0.1.5\node_modules\vextpack\dist\vuicc.exe ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:285:19)
at onErrorNT (node:internal/child_process:483:16)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
at onErrorNT (node:internal/child_process:483:16)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn ..\Documents\Battlefield 3\Server\Admin\Mods\mapeditor\WebUI\node_modules\.pnpm\vextpack@0.1.5\node_modules\vextpack\dist\vuicc.exe',
path: '..\Documents\Battlefield 3\Server\Admin\Mods\mapeditor\WebUI\node_modules\.pnpm\vextpack@0.1.5\node_modules\vextpack\dist\vuicc.exe',
spawnargs: [
'..\Documents\Battlefield 3\Server\Admin\Mods\mapeditor\WebUI\dist',
'..\ui.vuic'
]
}

Node.js v22.14.0
 ELIFECYCLE  Command failed with exit code 1.

Have tried removing package-lock.json and node_modules folder, installing again with no luck

Hey Islaiter,
Thx for your message back, It looks like you're running into an issue with it not being able to find the executable file, vuicc.exe. Here are a few steps that might help you.

Check the File Path
Make sure that the path to vuicc.exe is correct. You can navigate to this directory:
..\Documents\Battlefield 3\Server\Admin\Mods\mapeditor\WebUI\node_modules.pnpm\vextpack@0.1.5\node_modules\vextpack\dist\

Look for vuicc.exe is there... If it’s missing, it might mean the installation didn’t go through properly, or there might be permission issues :(

Reinstall the Package
You could try again reinstalling the package. Start by removing package-lock.json and the node_modules folder, then run these commands:

Clear the npm cache:

npm cache clean --force

Remove the node_modules directory and package-lock.json:

rm -rf node_modules package-lock.json

Install your dependencies again:

npm install

Check Your Package Manager
If you're using a package manager other than npm, like pnpm or yarn, make sure you're using the right commands for that manager.

For pnpm.
pnpm install

Look for the last Updates to
It's also a good idea to ensure that you're using the latest version of vextpack and any other relevant packages. You can check for outdated packages, with this command.

npm outdated

If you see any updates available, you might want to update your dependencies with.

4. npm install <package_name>@latest

Hopefully, one of these steps will help get things up and running! Let me know if you need any more help.

[islaiter]

Hello again and thanks for the help, unfortunately I didn't manage to make it work, following the steps you suggested, most dependencies wouldn't upgrade so I tried to install everything from the beginning again.

1. Removed mapeditor folder and all of its contents
2. Tried the install instructions from the readme, the set-up ones using vumm, got the following error:

https://vumm.bf3reality.com/api/v1/mods/mapeditor": x509: certificate signed by unknown authority

3. Downloaded the github files as zip (I'm using windows) and unzip them on

..\Documents\Battlefield 3\Server\Admin\Mods\mapeditor

4. Followed the steps under developer set-up and while using pnpm i, I got again a lot of deprecated packages warning
5. Got a list of all outdated dependencies using npm outdated
6. Removed node_modules folder and package.json while also cleaning npm cache as you suggested
7. Updated manually all dependencies that were outdated in package.json so it downloads the correct ones
8. Got still some warning for unmet peers

9. Tried to build again and this time got a huge list of errors, attached you will find a huge list of most of them, I guess this has to do with the unmet peers error while I tried to upgrade outdated dependencies.

errors.txt

[paulhobbel]

Hi @islaiter sorry for the long wait, this repo was a little bit unmaintained by our team. I am currently in the process of upgrading versions. I've already went through and fixed at least the packages