Custom Page - nodebb

[DownPW]

Personally, I don’t use custom routes in navigation. I put the link in a classic HTML href to access the page in an HTML menu of the BrandHeader, then I use the widget to generate the HTML for the page itself.

Seems you have problem with npm for uninstall the plugin in your screeshot

[Sampo2910]

Hi, thx for the reply. I managed to get the page up now. But still have a problem when trying to uninstall anything.

This is all a clean install.

[DownPW]

What is the error when you uninstall in nodebb log ?

[Sampo2910]

@DownPW

npm resolution error report

While resolving: grunt-contrib-watch@0.4.4
Found: grunt@0.3.17
node_modules/grunt
dev grunt@“^0.3.17” from the root project

Could not resolve dependency:
peer grunt@“~0.4.0” from grunt-contrib-watch@0.4.4
node_modules/grunt-contrib-watch
dev grunt-contrib-watch@“^0.4.4” from the root project

Conflicting peer dependency: grunt@0.4.5
node_modules/grunt
peer grunt@“~0.4.0” from grunt-contrib-watch@0.4.4
node_modules/grunt-contrib-watch
dev grunt-contrib-watch@“^0.4.4” from the root project

Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

[Sampo2910]

@DownPW

The debug.

0 verbose cli /home/smiley/.nvm/versions/node/v21.7.3/bin/node /home/smiley/.nvm/versions/node/v21.7.3/bin/npm
1 info using npm@10.9.1
2 info using node@v21.7.3
3 silly config load:file:/home/smiley/.nvm/versions/node/v21.7.3/lib/node_modules/npm/npmrc
4 silly config load:file:/home/smiley/nodebb/.npmrc
5 silly config load:file:/home/smiley/.npmrc
6 silly config load:file:/home/smiley/.nvm/versions/node/v21.7.3/etc/npmrc
7 verbose title npm uninstall nodebb-plugin-iframely
8 verbose argv “uninstall” “nodebb-plugin-iframely” “–save”
9 verbose logfile logs-max:10 dir:/home/smiley/.npm/_logs/2026-03-15T10_02_42_147Z-
10 verbose logfile /home/smiley/.npm/_logs/2026-03-15T10_02_42_147Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly logfile done cleaning log files
13 silly packumentCache heap:2197815296 maxSize:549453824 maxEntrySize:274726912
14 silly idealTree buildDeps
15 silly fetch manifest grunt@~0.4.0
16 silly packumentCache full:https://registry.npmjs.org/grunt cache-miss
17 http fetch GET 200 https://registry.npmjs.org/grunt 1238ms (cache revalidated)
18 silly packumentCache full:https://registry.npmjs.org/grunt set size:169561 disposed:false
19 verbose stack Error: could not resolve
19 verbose stack at PlaceDep.failPeerConflict (/home/smiley/.nvm/versions/node/v21.7.3/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/place-dep.js:503:25)
19 verbose stack at new PlaceDep (/home/smiley/.nvm/versions/node/v21.7.3/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/place-dep.js:157:21)
19 verbose stack at #buildDepStep (/home/smiley/.nvm/versions/node/v21.7.3/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:920:18)
19 verbose stack at async Arborist.buildIdealTree (/home/smiley/.nvm/versions/node/v21.7.3/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7)
19 verbose stack at async Promise.all (index 1)
19 verbose stack at async Arborist.reify (/home/smiley/.nvm/versions/node/v21.7.3/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5)
19 verbose stack at async Uninstall.exec (/home/smiley/.nvm/versions/node/v21.7.3/lib/node_modules/npm/lib/commands/uninstall.js:51:5)
19 verbose stack at async Npm.exec (/home/smiley/.nvm/versions/node/v21.7.3/lib/node_modules/npm/lib/npm.js:207:9)
19 verbose stack at async module.exports (/home/smiley/.nvm/versions/node/v21.7.3/lib/node_modules/npm/lib/cli/entry.js:74:5)
20 error code ERESOLVE
21 error ERESOLVE could not resolve
22 error
23 error While resolving: grunt-contrib-watch@0.4.4
23 error Found: grunt@0.3.17
23 error node_modules/grunt
23 error dev grunt@“^0.3.17” from the root project
23 error
23 error Could not resolve dependency:
23 error peer grunt@“~0.4.0” from grunt-contrib-watch@0.4.4
23 error node_modules/grunt-contrib-watch
23 error dev grunt-contrib-watch@“^0.4.4” from the root project
23 error
23 error Conflicting peer dependency: grunt@0.4.5
23 error node_modules/grunt
23 error peer grunt@“~0.4.0” from grunt-contrib-watch@0.4.4
23 error node_modules/grunt-contrib-watch
23 error dev grunt-contrib-watch@“^0.4.4” from the root project
23 error
23 error Fix the upstream dependency conflict, or retry
23 error this command with --force or --legacy-peer-deps
23 error to accept an incorrect (and potentially broken) dependency resolution.
24 error
24 error
24 error For a full report see:
24 error /home/smiley/.npm/_logs/2026-03-15T10_02_42_147Z-eresolve-report.txt
25 silly unfinished npm timer reify 1773568962435
26 silly unfinished npm timer reify:loadTrees 1773568962435
27 silly unfinished npm timer idealTree:buildDeps 1773568963186
28 silly unfinished npm timer idealTree:node_modules/grunt-contrib-watch 1773568963198
29 verbose cwd /home/smiley/nodebb
30 verbose os Linux 6.0.12-76060012-generic
31 verbose node v21.7.3
32 verbose npm v10.9.1
33 verbose exit 1
34 verbose code 1
35 error A complete log of this run can be found in: /home/smiley/.npm/_logs/2026-03-15T10_02_42_147Z-debug-0.log

[DownPW]

Which version of NodeBB do you have?

It doesn’t look like it’s recent, does it?

This error is caused by a Grunt version conflict.

It seems yiu currently uses grunt 0.3.17, but grunt-contrib-watch 0.4.4 requires grunt ~0.4.0. Modern npm versions (7+) are stricter with peer dependencies and will refuse to install conflicting versions.

have you try to bypass the error (common with old NodeBB installs):

npm install --legacy-peer-deps

or in your case:

npm uninstall nodebb-plugin-iframely --legacy-peer-deps

Maybe @phenomlab can help too

[Sampo2910]

@DownPW

npm install --legacy-peer-deps

I have tried already and still did not want to work.

npm uninstall nodebb-plugin-iframely --legacy-peer-deps

this got rid of iframely though.

[DownPW]

DownPW said:

Which version of NodeBB do you have?

It doesn’t look like it’s recent, does it?

This error is caused by a Grunt version conflict.

It seems yiu currently uses grunt 0.3.17, but grunt-contrib-watch 0.4.4 requires grunt ~0.4.0. Modern npm versions (7+) are stricter with peer dependencies and will refuse to install conflicting versions.

[Sampo2910]

@DownPW

Latest version of nodebb. Fresh install.

node is 21.7.3

npm is 10.9.1

[DownPW]

If you’re running the latest NodeBB version, then Node 21 and npm 10 are normally fine. Your error is most likely caused by a legacy dependency left over from an older install or from a plugin (probably something pulling grunt 0.3.x).

Modern NodeBB versions should not depend on old Grunt packages anymore, so something in your dependency tree is outdated.

---

What is probably happening

You likely have:

• Latest NodeBB
• Modern Node/npm
• Old dependency still present

Usually caused by:

• an old plugin
• an upgrade from an older NodeBB version
• a package.json that was never fully cleaned

Recommended clean fix

Do a clean reinstall of dependencies:

cd ~/nodebb
rm -rf node_modules
rm package-lock.json
npm cache clean --force
npm install

If it still fails

Try:

npm install --legacy-peer-deps

This is sometimes necessary when plugins have outdated peer dependencies.

Also check your installed plugins

Run:

./nodebb plugins

Often the issue comes from an outdated plugin (possibly nodebb-plugin-iframely since you were uninstalling it or other.

Reliable NodeBB admin fix procedure

A typical safe rebuild process:

./nodebb stop
rm -rf node_modules package-lock.json
npm install --legacy-peer-deps
./nodebb build
./nodebb start

if the problems persist maybe open a thread at nodebb communauty

[Sampo2910]

@DownPW Sorry for late reply. But, thank you so much. All is working ok again

cd ~/nodebb
rm -rf node_modules
rm package-lock.json
npm cache clean --force
npm install

This worked perfectly. Much appreciated your help.

[DownPW]

I’m happy to see this