-
Notifications
You must be signed in to change notification settings - Fork 19
Support publishing new udaru packages to npm #496
Conversation
…ed to add to release the postgres client.
…u, udaru-hapi-plugin -> @nearform/udaru-hapi-plugin
|
||
### Stand alone server | ||
``` | ||
$ npx udaru |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is npx correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes it is (see https://medium.com/@maybekatz/introducing-npx-an-npm-package-runner-55f7d4bd282b)
This is not tested though but the intent is to be able to run it via npx
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me Damien, fair play!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM only one small comment
|
||
1) `udaru-core` - the core udaru library | ||
|
||
2) `udaru-hapi-plugin` - a plugin for Hapi that exposes a HTTP interface to `udaru-core` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hapi
should be written as hapi.js
We will be publishing the 3 new packages as the following npm modules:
The existing npm.im/udaru module in npm will be used for the standalone server. The other two packages are new and will be published under the @nearform name space. (Thanks to @mcollina for advising on this).
The above naming convention also give us scope in the future for developing fastify or express http wrappers around core.
This PR supports the above, it's a combination of:
require
statements everywhereudaru-core
addedMore tidy up (particularly around documentation) to follow before we actually publish.