node-coap | CoAP - Node.js style | Runtime Evironment library

I don't think there is any plugin as of today that supports CoAP. You might want to write one.

A quick search shows there are native clients available on respective platforms, iCoAP / spitfirefox for which you could write a plugin or directly use the apis in your project.

Read more about accessing native or third party libraries in iOS / Android from the docs.

Vue.js can use NPM library, i.e. a library that was published on NPM registry and is installed with NPM or Yarn package managers.

There's no strict definition of Node library. Usually this means that a library is intended to be used in Node.js and uses Node.js features. Sometimes it's possible to mock or polyfill them on client side (streams, buffers). Package internals should be examined in order to make a decision. E.g. joi is Node library but doesn't depend on Node.js features for the most part and is suitable for browser use with a few adjustments at build step.

node-coap documentation clearly states that the package uses Node.js http module, which isn't available on client side:

client and server library for CoAP modeled after the http module

Notice that it refers to CoAP client, not to client-side environment (a browser).

Since Vue.js supports server-side rendering, it's possible to use Node libraries on server side. This will work if some units don't need to be used on client side or they are used differently (load data from filesystem on server side and via AJAX request on client side). This approach won't work in this case because Node.js library functionality is needed on client side.

If you want to communicate with a oneM2M CSE from your application, then you should implement the Mca interface. This is the interface between a CSE and your application, technically called an Application Entity, or AE.

The simplest way is to use the REST binding. You may have a look at the oneM2M's developer guide at http://www.onem2m.org/application-developer-guide.

You also might want to read the following specifications:

• TS-0001: Functional Specification, which is the core specification document of oneM2M. Here, the basic concepts as well as all resource types are defined.
• TS-0004: Service Layer Core Protocol for further details on the actual encodings and representation of resources.
• TS-0008: CoAP Protocol Binding
• TS-0009: HTTP Protocol Binding

You can find the latest version of these and other specifications here: http://www.onem2m.org/technical/published-documents

In the node-coap readme, an example of setOption uses a numeric name for the custom option.

There is an example there in their repo:

https://github.com/mcollina/node-coap/blob/master/examples/req_with_payload.js

It can't as long you are using UDP as transport.

As per RFC7252:

As CoAP is bound to unreliable transports such as UDP, CoAP messages may arrive out of order, appear duplicated, or go missing without notice. For this reason, CoAP implements a lightweight reliability mechanism, without trying to re-create the full feature set of a transport like TCP. It has the following features:

• Simple stop-and-wait retransmission reliability with exponential back-off for Confirmable messages.

• Duplicate detection for both Confirmable and Non-confirmable messages.

https://tools.ietf.org/html/rfc7252

There are some efforts to make CoAP-over-HTTP in different implementations but it does not belong to CoAP RFC itself.

You may try to dig in this way if you absolutely forced to use CoAP.