* Add MQTT via WebSocket communication option
Add option in MQTT broker configuration node to enable MQTT via WebSoket comunication
* MQTT over WS error correction
Minimal correction of values and erase debug console.log unnecessary
* original package.json
Erase some changes on grunt build at package.json. Erase package-lock.json and back to the original package.json
* .gitignore
* .gitignore again
* No tabs
* initial support of SORT node
minor fix of sort node
fixed error message of sort node
fixed error handling of SORT node
add test case for SORT node
make limit of messages count computed once in SORT node
* update type in message & info description
* fix handling of pending messages in SORT node
* initial support of SORT node
minor fix of sort node
fixed error message of sort node
fixed error handling of SORT node
add test case for SORT node
make limit of messages count computed once in SORT node
* update type in message & info description
* updates to 80-template to allow setting template with msg.template
* updated 80-template_spec test for msg.template support
* fixed 80-template.js test
So far, for typedInput "<input type=text>" fields, only custom styles like "width:100%" or "width:75px" worked. Proposed change allows to use calc() as well like in "width:calc(100% - 120px)"
* Let trigger node support per topic mode
* ensure trigger node clones repeating message
* Add some tests for trigger by topic
* test trigger repeat for pass by ref error
* trigger test - add missing try/catch to all test with callback
* boost trigger node test coverage
* Call fsync() before closing file
* Fix race condition in tests due to incorrect stub.
The startFlows() function wasn't really being stubbed, so it was still being called. But there was no corresponding call to stopFlows().
In later tests, the check in Flows.init() was throwing the "Cannot init without a stop" error.
* Test coverage for fsync() calls
For issue #1478
* Revert "Fix race condition in tests due to incorrect stub."
This reverts commit 4f71d7851b.
* Fix race condition in tests due to incorrect stub.
The startFlows() function wasn't really being stubbed, so it was still being called. But there was no corresponding call to stopFlows().
In later tests, the check in Flows.init() was throwing the "Cannot init without a stop" error.
* Fix intermittent test failure in Exec node.
Occasionally, the error text on stderr will come in more than one piece. The test only worked correctly if a single message was received.
* Add rc property to exec node outputs 1 and 2
to close#1399
* improve test coverage and add tests for new msg.rc
* make spawn test slightly more robust to different environments
* added debug for spawn test
* let spawn error test be even more relaxed
* don't necessarily clone msg.payload in exec node stderr
as per suggestion
* Fix a problem of file append test on Windows
* Skip the test case of file node that fails on Windows
* Remove close() call
* Fixed a recreated file test case on Windows
