Windows npm start: Plugin not Found (Blocking)

[doc-code-hub]

Edited

As of now (1/16/2022), I still haven't found a way to make the project work with windows (despite the node and npm versions match).

The only solution that allowed me to work on the project on a windows PS was, as kindly suggested by @ferferga, to use WSL as a development environment.

Hope this helps someone save time wasted with Windows (11 in my case)

---

Original

Hi everyone.

Hope it's the right place to ask for help!

I am trying to launch the project locally but I am having a (blocking) problem with plugins.

I usually work with other frontend frameworks. I don't know if I'm missing some passages that are not in the README.md.

My npm i logs:

Technical Data:

System: Windows 11
Node -v: 16.13.1
npm -v: 8.1.2

Thanks in advance for any help!

[martadinata666]

afaik need to build first before start, npm run build && nuxt start src aka npm run prod
https://github.com/jellyfin/jellyfin-vue/blob/master/package.json

[doc-code-hub]

Thank you for your time!

Actually, doing so, I get the same error :(

Also I believe that in this case the README should indicate it, to avoid getting errors following the instructions.
However, this does not seem to be the case...

[martadinata666]

I tried from clean git clone, can confirm that no issue.

debian@9e32e413aa30:/$ cd ~/jellyfin-vue/
debian@9e32e413aa30:~/jellyfin-vue$ ls
codecov.yml  commitlint.config.js  CONTRIBUTING.md  Dockerfile  jest.config.js  LICENSE  package.json  package-lock.json  README.md  src  stylelint.config.js  tsconfig.json  vetur.config.js
debian@9e32e413aa30:~/jellyfin-vue$ npm install
npm WARN invalid config lockfile-version="3" set in /home/debian/jellyfin-vue/.npmrc
npm WARN invalid config Must be one of: null, 1, 2, 3
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jellyfin/frontend-vue@0.0.0',
npm WARN EBADENGINE   required: {
npm WARN EBADENGINE     node: '>=16.13.1 <17.0.0',
npm WARN EBADENGINE     npm: '>=8.1.2',
npm WARN EBADENGINE     yarn: 'Yarn is not supported. Please use NPM.'
npm WARN EBADENGINE   },
npm WARN EBADENGINE   current: { node: 'v16.13.0', npm: '8.1.0' }
npm WARN EBADENGINE }
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated @types/browserslist@4.15.0: This is a stub types definition. browserslist provides its own type definitions, so you do not need this installed.
npm WARN deprecated @types/anymatch@3.0.0: This is a stub types definition. anymatch provides its own type definitions, so you do not need this installed.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

> @jellyfin/frontend-vue@0.0.0 prepare
> husky install

husky - Git hooks installed

added 2148 packages, and audited 2149 packages in 3m

102 vulnerabilities (94 moderate, 6 high, 2 critical)

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

To address all issues possible (including breaking changes), run:
  npm audit fix --force

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

Run `npm audit` for details.
npm notice 
npm notice New minor version of npm available! 8.1.0 -> 8.3.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.3.0
npm notice Run npm install -g npm@8.3.0 to update!
npm notice 
debian@9e32e413aa30:~/jellyfin-vue

debian@ca8e762a1ed8:~/jellyfin-vue$ npm start
npm WARN invalid config lockfile-version="3" set in /home/debian/jellyfin-vue/.npmrc
npm WARN invalid config Must be one of: null, 1, 2, 3
⸨⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⸩ ⠏ : timing npm:load:cleanupLog Completed in 7ms
> @jellyfin/frontend-vue@0.0.0 start
> nuxt src

⸨⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⸩ ⠏ : timing npm:load:cleanupLog Completed in 7ms
   ╭────────────────────────────────────────╮
   │                                        │
   │   Nuxt @ v2.15.8                       │
   │                                        │
   │   ▸ Environment: development           │
   │   ▸ Rendering:   client-side           │
   │   ▸ Target:      server                │
   │                                        │
   │   Listening: http://172.19.0.2:3000/   │
   │                                        │
   ╰────────────────────────────────────────╯

ℹ Preparing project for development                                                                                                                                                                                               19:15:02
ℹ Initial build may take a while                                                                                                                                                                                                  19:15:02
ℹ Discovered Components: src/.nuxt/components/readme.md                                                                                                                                                                           19:15:02
✔ Builder initialized                                                                                                                                                                                                             19:15:02
✔ Nuxt files generated                                                                                                                                                                                                            19:15:02

✔ Client
  Compiled successfully in 3.41m

No issues found.                                                                                                                                                                                                                  19:18:33
ℹ Waiting for file changes                                                                                                                                                                                                        19:18:37
ℹ Memory usage: 964 MB (RSS: 1.34 GB)                                                                                                                                                                                             19:18:37
ℹ Listening on: http://172.19.0.2:3000/

[doc-code-hub]

Thanks again!

Are you using my same versions?
System: Windows 11
Node -v: 16.13.1
npm -v: 8.1.2

Are you using nvm for windows?

I also tried again on a fresh clone but the situation is still the same.

Among other things I mention that on windows I am using NVM (https://github.com/coreybutler/nvm-windows) for the versioning of node and npm.

I'm starting to think it may be part of the problem.

On an ubuntu server, I was able to launch the project with no blocking issues, both locally and for a build prod.

Here on Windows 11, with NVM (and the minimum versions that match what is indicated in the README.md) is not working.

[martadinata666]

So im trying the windows. Using nodesource installer instead nvm-manager

PS C:\Users\dedyms\Documents\jellyfin-vue> npm start

> @jellyfin/frontend-vue@0.0.0 start
> nuxt src


   ╭─────────────────────────────────────────╮
   │                                         │
   │   Nuxt @ v2.15.8                        │
   │                                         │
   │   ▸ Environment: development            │
   │   ▸ Rendering:   client-side            │
   │   ▸ Target:      server                 │
   │                                         │
   │   Listening: http://192.168.0.9:3000/   │
   │                                         │
   ╰─────────────────────────────────────────╯

i Preparing project for development                                                                                                                                                                    20:42:47
i Initial build may take a while                                                                                                                                                                       20:42:47
i Discovered Components: src/.nuxt/components/readme.md                                                                                                                                                20:42:48
√ Builder initialized                                                                                                                                                                                  20:42:48
√ Nuxt files generated                                                                                                                                                                                 20:42:48

* Client █████████████████████████ building (68%) 2556/2609 modules 53 active
 css-loader » postcss-loader » sass-loader » node_modules\vuetify\src\styles\styles.sass


× Client
  Compiled with some errors in 1.08m


 ERROR  Failed to compile with 3 errors                                                                                                                                                friendly-errors 20:43:54
* Client █████████████████████████ building (68%) 2645/2690 modules 45 active
These dependencies were not found:                                                                                                                                                     friendly-errors 20:43:54
                                                                                                                                                                                       friendly-errors 20:43:54
* env in ./node_modules/libass-wasm/dist/js/subtitles-octopus-worker.wasm                                                                                                              friendly-errors 20:43:54
* fs in ./node_modules/libass-wasm/dist/js/subtitles-octopus-worker.js                                                                                                                 friendly-errors 20:43:54
* wasi_snapshot_preview1 in ./node_modules/libass-wasm/dist/js/subtitles-octopus-worker.wasm                                                                                           friendly-errors 20:43:54
                                                                                                                                                                                       friendly-errors 20:43:54
To install them, you can run: npm install --save env fs wasi_snapshot_preview1                                                                                                         friendly-errors 20:43:54
No issues found.                                                                                                                                                                                       20:43:55

 WARN  Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'                                                                                                  20:43:57

i Waiting for file changes                                                                                                                                                                             20:44:02
i Memory usage: 1.04 GB (RSS: 1.63 GB)                                                                                                                                                                 20:44:02
i Listening on: http://192.168.0.9:3000/                                                                                                                                                               20:44:02
Terminate batch job (Y/N)? Y

A whole difference error than yours 🤦🏼 not familiar with nodejs windows so cant really tell what happen.

[doc-code-hub]

JUST FOR THE RECORD

I tried to move the project to the desktop (from my old A:... location) , and now I'm getting exactly the same error you posted! (Indeed, it radically changes the error based on the location of the project as @ferferga said)

In this case, the listener on port 3000 is able to start, however, the errors indicated by the console are immediately shown.

And you are not using nvm (as you were saying) ...

Is there any developer working on the project from Windows (10/11 without using WLS) successfully?

[ferferga]

What's the problem with WSL?

[doc-code-hub]

No problem, as i was sayng to you i will try that. I was just wondering if anyone had succeeded without WLS (Like I was hoping to)

[ferferga]

There's nothing missing in readme: it's a simple npm i (or npm install) npm start.

The npm run prod is for building a production version of the client and serving it within nuxt (as indicated in the instructions)

It has something to do with your particular environment. Clone the project again (or run git clean -fxd and git reset --hard) and run the above commands again (depends on if you want to start developing or want to directly build and test a production version).

Additionally, there seems to be some oddities in your setup:

• You're using the A drive for storing the data. Historically, that mountpoint in windows was for floppy disks and might have some incompatibilities with modern applications.

Additionally, you can use Docker to build the project or use our images.

[doc-code-hub]

Thanks.
I didn't know about this historical fact on windows related to mount point A:. Interesting.

i tried to clone again but i get the same

Anyway I keep all my projects on that drive and have never had such problems (but I work with node 12, 14 usually).
Maybe something that has to do with node 16 and A: \ ... Strange ...

However as I said, on my Ubuntu Server 20.04 environment I was able to launch and build the project without any difficulty using the same versions of NODE and NPM.

I believe I will try to work with Remote Development directly on the machine.

I was just hoping someone was familiar with my problem so that I could work on it on my personal Windows environment.

If I find a solution to my own problem, I will come back here to write it hoping to be able to help someone else in the future.

Thanks again

[ferferga]

My main rig is in Windows but I use WSL because node in my experience starts accumulating a lot of trash and the environment gets polluted easily.

With WSL you have the advantages of Docker and a VM without the added cognitive stuff of thinking of mountpoints, etc. And cleaning up is ats easy as uninstall the app from MS Store and reinstall

[doc-code-hub]

Thank you for your suggestion!

I don't know it yet but now I intend to try it.

I hope to be able to run the project on my main Windows!

[ferferga]

This has been fixed already but not closed.

We now have CI checks in place to test builds in all platforms to prevent regressions like these.