doug kimmerly - npm link issue . I just starte...
npm link issue . I just started a new project today on version 2.13.2 brand new install on pi5. When I set up the npm link and restart the server I can see the new link in the node_modules directory, but no new plugin in the plugin config and no error or other messages from that code in the server log. When I've done this in the past it instantly shows up ??? I also tested by downloading a known good plugin from github set up the link and the same thing no errors and no config. So then I tried the same known good plugin on my production server and same results. I'm starting to think it's not just my poor coding. All ideas and suggestions welcome.
8 Replies
Can you show the commands you are running and in which directories?
I do this on a daily basis without issue, so chances are that something is wrong with your commands.
From my working directory /home/doug/testplugin I run "sudo npm link" then from /home/doug/.signalk I run "sudo npm link testplugin" then restart the server. It creates the link just fine in the node_modules directory but then nothing shows in the config
Not sure if it matters, but don’t need sudo in the second command
There are no errors in server log at startup?
no errors at all
On my phone, so can’t do much
There is a debug for plugins, something like interfaces:plugins
Might show something…
ok thanks I'll be at it again tomorrow
it was all me I didn't have the signalk-node-server-plugin keyword in the package.json file. Thanks for the response and help the logger helped me figure it out.
I didn't even think of that since you said that you tried another plugin too...