subscriber's event function ctx with different structure

[lling1105]

i have 2 clients subscribe the same event, when both receive the notice, one has ctx and can get the params correctlly, but the other one ctx is the params value, no params path, why?

both client service with the same codes,
#1 client event receiver:
ctx.params -> {"result":"ok"}

#2 client event receiver:
ctx -> {"result":"ok"} and no ctx.params

[AndreMaz]

Hi @lling1105 can you create a repro repo please?

[lling1105]

@AndreMaz this issue appeared when use webpack.js to build bundle.js, guess it's about the output setting: libraryTarget: 'commonjs2'. i changed to other kind target, but still the same

[lling1105]

solved! set webpack optimization.minimizer to none

[ngraef]

This seems like it's related to moleculer's support for two different function signatures for event handlers (see the 0.14 changelog). The code that determines which signature to use relies on the name of the parameter being ctx or context:

moleculer/src/service.js

Lines 32 to 34 in 422876c

	function isNewSignature(args) {
	return args.length > 0 && ["ctx", "context"].indexOf(args[0].toLowerCase()) !== -1;
	}

Webpack (or any other) minimizer will usually change the parameter name, causing the function to be passed params for the old event handler signature. As the changelog notes, you can add context: true to the event definition to force the new signature if you want to continue using a minimizer.

[icebob]

Exactly.