As of Oracle Digital Assistant 19.4.1, the local deployment of custom components has changed to the point that custom component tar balls (“.tgz” files) must now contain all node module dependencies. This change addresses the new Acceptable Use of the Public Registry announcement by NPM , Inc.
The blog article referenced in this post explains everything you need to know about this deployment change and provides guidance on what to do or not to do.
What Has Changed
In previous versions of Oracle Digital Assistant, deployment packages contained only the custom component service sources and the package.json file that lists the node module dependencies. During deployment, the Oracle Digital Assistant skill then called ‘npm install’ on the package to install dependent Node modules from the Internet. With the new deployment model in Oracle Digital Assistant 19.4.1 and later, the dependent Node modules must be deployed with the custom components.
What You Need to Know: Creating New Custom Component Packages
In version 2.2.2 of its Oracle Bots Node SDK ( https://github.com/oracle/bots-node-sdk), Oracle has changed the deployment to include dependent Node modules in the deployable package. The Oracle Bots Node SDK is the recommended option for you to build and deploy custom components, as well as webhook clients. Read the complete article here.
For regular information become a member in the Developer Partner Community please register here.
Blog 
Twitter 
LinkedIn ![image[7][2][2][2]](https://soacommunity.files.wordpress.com/2013/04/image7222.png?w=20&h=20 "image[7][2][2][2]"){kind=small}
Facebook 
Meetups
Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic
Developer Community 