implicit redis dependence causes issues with webpack builds about openwhisk-composer HOT 3 CLOSED

I am not sure I understand the issue. Redis does not appears in package.json dependencies because composer does not require redis. The execution of the conductor action code generated by composer may require redis, but does not require composer... The redis dependency must be satisfied by the openwhisk runtime image, not the composer install.

Are you saying that webpack detects the require statement, which causes a problem for kui?

I can obfuscate the require('redis') bit if you tell me how to fool webpack.

from openwhisk-composer.

webpack sees an import of composer/client, which in turn imports ./conductor, which in turn imports (possibly) redis, which leads to a webpack build error.

option 1) isolate the conductor and client code, so that use of the client does not chain-import conductor.js

option 2) if hacks are necessary, i think you can defeat the webpack dependence crawl by doing a string-import, something like

const redis = 'redis'
require(redis)

from openwhisk-composer.

oh, i think you can also add webpack magic comments:

require('/* webpackIgnore: true */ redis')

from openwhisk-composer.