Forum wide moderators
Node 8 and npm@5 can work with custom plugins, but you should be using npm@5.3 minimum and npm link.
Let's say you have a directory called web with the nodebb directory within it. Clone your custom plugin repositories into web (so there's, for instance web/nodebb-plugin-customized-by-you), and then run npm link inside the plugin repository directory, and then npm link nodeb-plugin-customized-by-you in the nodebb directory.
@teh_g the reason it happens with node 8 is that npm@5 comes with node 8. This issue is caused by npm@5
@julian you may want to take this to stack overflow. This is a forum for NodeBB, the node based forum software, not a forum for node.js
Updated to v0.3.0
Finally got this guy working.
Not quite stable yet, but very soon.
It's just a warning. Ignore it. No need to rollback. It's supposed to show a warning only when any installed plugins use String.prototype.rtrim but the way it's setup... NodeBB shows the warning even when it's not used.
I'm thinking that you didn't remove the existing define call inside the file. At the end of the file is
"function"==typeof define&&define.amd?define([],C)
You need to change that to
"function"==typeof define&&define.amd?define('iFrameResizer', [],C)
Instead of doing the wrapper thing you said you're doing.
You have to do this for the last one:
<script type="text/javascript">
require(['iFrameResize'], function (iFrameResize) {
iFrameResize({
log: true
});
});
</script>
npm install npm@4 -g should also fix this issue