Dependencies update

[sinamics]

Updated:

• next.js to 15.1.2
• next-auth to 4.24.5
• next-intl to 3.1.4
• prisma-adapter to 1.0.5
• trpc to 10.37.1

Resolves #611

[sinamics]

@tinola does these updates make any issues for FreeBSD ?

[tinola]

@tinola does these updates make any issues for FreeBSD ?

Well, yes, let me check... For now build failed because of no vips installed ;) Installing vips-nox11... I'll be back with feedback

[tinola]

@tinola does these updates make any issues for FreeBSD ?

OK, here's a solution:

1. Install vips-nox11 package
2. Do clean pull of ztnet from github - build process fails:

> [email protected] build
> next build

 ⚠ Invalid next.config.mjs options detected:
 ⚠     Unrecognized key(s) in object: 'swcMinify'
 ⚠ See more info here: https://nextjs.org/docs/messages/invalid-next-config
   ▲ Next.js 15.1.2
   - Environments: .env

   Skipping linting
 ✓ Checking validity of types
   Creating an optimized production build ...
   Using cached swc package @next/swc-wasm-nodejs...
Failed to compile.

./docs/images/logo/ztnet_200x178.png
Error: Could not load the "sharp" module using the freebsd-x64 runtime
Possible solutions:
- Manually install libvips >= 8.15.3
- Add experimental WebAssembly-based dependencies:
    npm install --cpu=wasm32 sharp
    npm install @img/sharp-wasm32
- Consult the installation documentation:
    See https://sharp.pixelplumbing.com/install
    at Object.<anonymous> (/home/ztnet/ztnet/node_modules/sharp/lib/sharp.js:113:9)
    at Module._compile (node:internal/modules/cjs/loader:1364:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
    at Module.load (node:internal/modules/cjs/loader:1203:32)
    at Module._load (node:internal/modules/cjs/loader:1019:12)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at mod.require (/home/ztnet/ztnet/node_modules/next/dist/server/require-hook.js:65:28)
    at require (node:internal/modules/helpers:177:18)
    at Object.<anonymous> (/home/ztnet/ztnet/node_modules/sharp/lib/constructor.js:10:1)
    at Module._compile (node:internal/modules/cjs/loader:1364:14)

Import trace for requested module:
./docs/images/logo/ztnet_200x178.png
./src/components/layouts/header.tsx
./src/components/layouts/layout.tsx
./src/pages/admin/controller/index.tsx

3. What is interesting from above build output:

- Manually install libvips >= 8.15.3
- Add experimental WebAssembly-based dependencies:
    npm install --cpu=wasm32 sharp
    npm install @img/sharp-wasm32`

Well, vips-nox11 is installed, so let's fire up these 2 npm install commands.
The first one:

# npm install --cpu=wasm32 sharp

added 2 packages, and audited 835 packages in 2s

121 packages are looking for funding
  run `npm fund` for details

6 vulnerabilities (3 low, 2 moderate, 1 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

The second one:

# npm install @img/sharp-wasm32
npm error code EBADPLATFORM
npm error notsup Unsupported platform for @img/[email protected]: wanted {"cpu":"wasm32"} (current: {"cpu":"x64"})
npm error notsup Valid cpu:  wasm32
npm error notsup Actual cpu: x64
npm error A complete log of this run can be found in: /home/ztnet/.npm/_logs/2024-12-21T19_29_10_909Z-debug-0.log

Hmm, the second npm install seems to be in some case misleading, because ztnet was successfully built and running :)