Registry / communication / node-red-aquila

node-red-aquila

JSON →
library0.3.0jsnpmunverified

Node-RED nodes for Aquila's IoT platform, version 0.3.0. Provides integration with Aquila, makerslab, and Altair IoT services within Node-RED. Installation requires Node-RED user directory and may be done locally or globally. The package is lightweight and specific to the Aquila ecosystem, not actively maintained.

npm install node-red-aquila
INSTALL
IMPORT
SIG · NODE-RED-AQUILA
N
node-red-aquila
communicationjavascriptv0.3.0
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

AQ_Node
const AQ_Node = require('node-red-aquila').AQ_Node
import { AQ_Node } from 'node-red-aquila'
Node-RED environments typically use CommonJS require() in Node.js.
aquilaNode
const { aquilaNode } = require('node-red-aquila')
const aquilaNode = require('node-red-aquila')
Be careful to destructure if only one is needed.
default
const Aquila = require('node-red-aquila')
import Aquila from 'node-red-aquila'
The package exports a namespace object, not a default export.

Shows how to manually register an Aquila node type in Node-RED using CommonJS require and registerType.

// In Node-RED function node or settings.js const Aquila = require('node-red-aquila'); // Node-RED will auto-discover nodes if installed correctly. // Manual registration example: RED.nodes.registerType('aquila-out', Aquila.aquilaNode);
Debug
Known issues
gotchaInstallation must be from Node-RED user directory (~/.node-red) or globally, otherwise nodes are not detected.
fix
Run 'cd ~/.node-red && npm install node-red-aquila' or use global install with -g.
affects: all
deprecatedUsing 'npm install -g' to install Node-RED nodes globally may cause version conflicts with other Node-RED instances.
fix
Prefer local installation in ~/.node-red directory.
affects: <0.3.0
breakingThe package may not be compatible with Node-RED 3.x due to changes in node registration API.
fix
Check for updates or fork and update node registration calls.
affects: >=3.0
Errors
Common errors & fixes
Error: Cannot find module 'node-red-aquila'
Node-RED cannot locate the package; likely installed in wrong directory or not installed.
fix
Ensure npm install is run from ~/.node-red directory.
TypeError: RED.nodes.registerType is not a function
Trying to use registerType outside of Node-RED context or before RED is available.
fix
Use registerType only in Node-RED settings.js or within a Node-RED plugin context.
Error: The module 'node-red-aquila' is not a Node-RED module
Node-RED failed to load the module because it lacks proper package.json node-red section.
fix
Ensure package.json contains 'node-red' key with nodes array.
Upgrade
Version history
0.3.0latest on npm
Audit
Dependencies
node-redoptionalRuntime dependency; nodes are loaded by Node-RED
Agent activity
9 hits · last 30 days
node
8
OpenAI (training)
1
Resources
node-red-aquila — npm install node-red-aquila · libregistry