Deepmerge is not a function

[pacey]

Version: 2.9.1
Node version: 6.10
Environment: AWS Lambda

I'm having trouble with a transitive dependency that this project is using called deepmerge, via rest-facade. At runtime I get an error deepmerge is not a function.

[luisrudge]

does it work in your machine (not in lambda)?

[pacey]

It's hard to run locally, but using a tool called sam local it spins up a docker container with a similar execution environment to that of Lambda.

Sam local output:

2018/02/01 14:19:41 Successfully parsed cfn.yaml
2018/02/01 14:19:41 Connected to Docker 1.35
2018/02/01 14:19:41 Fetching lambci/lambda:nodejs6.10 image for nodejs6.10 runtime...
nodejs6.10: Pulling from lambci/lambda
Digest: sha256:b72789e8a544e658a76d71a0abbb2fa8b4122cc882bcd27097037bd28f657c9b
Status: Image is up to date for lambci/lambda:nodejs6.10
2018/02/01 14:19:42 Invoking  (nodejs6.10)
2018/02/01 14:19:42 Decompressing /Users/jamespace/Development/notification-service/dist/orderCreated/orderCreated.zip
2018/02/01 14:19:42 Mounting /private/var/folders/90/hw3fsjqj13v6b8kghq_q6xyh0000gn/T/aws-sam-local-1517494782706213000 as /var/task:ro inside runtime container
START RequestId: 0325e4c4-b25e-1b92-5aff-6382504037c8 Version: $LATEST
2018-02-01T14:19:42.714Z	0325e4c4-b25e-1b92-5aff-6382504037c8	{}
2018-02-01T14:19:42.716Z	0325e4c4-b25e-1b92-5aff-6382504037c8	{"errorMessage":"deepmerge is not a function","errorType":"TypeError","stackTrace":["new Client (/var/task/index.js:83164:18)","new OAuthAuthenticator (/var/task/index.js:116108:16)","new AuthenticationClient (/var/task/index.js:44973:16)","new ManagementTokenProvider (/var/task/index.js:116004:31)","new ManagementClient (/var/task/index.js:63767:26)","/var/task/index.js:63619:12","process._tickDomainCallback (internal/process/next_tick.js:135:7)"]}
END RequestId: 0325e4c4-b25e-1b92-5aff-6382504037c8
REPORT RequestId: 0325e4c4-b25e-1b92-5aff-6382504037c8	Duration: 997.09 ms	Billed Duration: 1000 ms	Memory Size: 128 MB	Max Memory Used: 130 MB

AWS Lambda output:

Function Logs:
START RequestId: 40820935-074d-11e8-a139-6bc76e506aec Version: $LATEST
2018-02-01T12:41:41.113Z	40820935-074d-11e8-a139-6bc76e506aec	{}
2018-02-01T12:41:41.113Z	40820935-074d-11e8-a139-6bc76e506aec	{"errorMessage":"deepmerge is not a function","errorType":"TypeError","stackTrace":["new Client (/var/task/index.js:83164:18)","new OAuthAuthenticator (/var/task/index.js:116108:16)","new AuthenticationClient (/var/task/index.js:44973:16)","new ManagementTokenProvider (/var/task/index.js:116004:31)","new ManagementClient (/var/task/index.js:63767:26)","/var/task/index.js:63619:12","process._tickDomainCallback (internal/process/next_tick.js:135:7)"]}
END RequestId: 40820935-074d-11e8-a139-6bc76e506aec
REPORT RequestId: 40820935-074d-11e8-a139-6bc76e506aec	Duration: 12.60 ms	Billed Duration: 100 ms 	Memory Size: 512 MB	Max Memory Used: 131 MB	

The call that triggers this error is constructing a new instance of the ManagementClient:

new auth0.ManagementClient({
    domain: "xxxxx",
    clientId: "xxxxx",
    clientSecret: "xxxxx",
    scope: "read:user"
})

[pacey]

I think I am falling foul of this issue - webpack/webpack#5756 which is probably just a bug with the deepmerge package 👎

[TehShrike]

It is not a bug in deepmerge. See TehShrike/deepmerge#92 (comment) + TehShrike/deepmerge#87 (comment)

[luisrudge]

Do you have a stack trace? We don't use deepmerge directly, so it's probably a dependency

[pacey]

The stack trace references my webpack bundled code so it's not massively helpful, but it does have the class names in so I'll add it below. The library is coming in from the dependency on rest-facade. Here is the stack trace anyways:

Response:
{
  "errorMessage": "deepmerge is not a function",
  "errorType": "TypeError",
  "stackTrace": [
    "new Client (/var/task/index.js:83164:18)",
    "new OAuthAuthenticator (/var/task/index.js:116108:16)",
    "new AuthenticationClient (/var/task/index.js:44973:16)",
    "new ManagementTokenProvider (/var/task/index.js:116004:31)",
    "new ManagementClient (/var/task/index.js:63767:26)",
    "/var/task/index.js:63619:12",
    "process._tickDomainCallback (internal/process/next_tick.js:135:7)"
  ]
}

[luisrudge]

https://github.com/ngonzalvez/rest-facade/blob/82b14e0ed0d9227f192471bf59c987ef16fa10e4/src/Client.js#L4

This looks like a pretty standard require to me, but maybe the rest-facade owner has more info about it. I'll close it since it's not related with this project.

[pacey]

Maybe, but the end result is that I can't use this library in my application. Which is shame as we are currently storing all our user data in Auth0.

[luisrudge]

You absolutely can use it. The SDK itself works as expected. What you're having is an environment issue, not an SDK issue.

[luisrudge]

Unfortunately, I don't know enough about aws lambda to help you fix this issue :(

[pacey]

Lambda aside, I think building the webpack bundle is where it's tripping up. It's a very basic webpack build that creates a bundle targeting commonjs2. I've tried various ways of requiring the library e.g. import { ManagementClient } from "auth0", const ManagementClient = require("auth0").ManagementClient; but nothing seems to work.

[shankie-codes]

I'd just like to add my support to Pacey. I'm having the same issue, but on a normal Node 7 environment –– and I'm not using rest-facade.

My stack trace looks like this:

TypeError: deepmerge is not a function
    at new Client (/usr/src/app/dist/server.bundle.js:625608:18)
    at new ClientsManager (/usr/src/app/dist/server.bundle.js:645120:19)
    at new ManagementClient (/usr/src/app/dist/server.bundle.js:612845:18)
    at /usr/src/app/dist/server.bundle.js:612653:24
    at Generator.next (<anonymous>)
    at step (/usr/src/app/dist/server.bundle.js:612632:191)
    at /usr/src/app/dist/server.bundle.js:612632:437
    at /usr/src/app/dist/server.bundle.js:612632:99
    at tokenManager.getToken.then (/usr/src/app/dist/server.bundle.js:612663:19)
    at process._tickDomainCallback (internal/process/next_tick.js:135:7)

Is it possible that both node-auth0 and another dependency are somehow importing packages in ways that conflict?

[luisrudge]

as with any npm package, everything is possible 😝 can you reproduce with only node-auth0? Or this only happens in your app, which you have some other dependencies?

[TehShrike]

Apparently most of the people reporting issues in TehShrike/deepmerge#87 were using TypeScript - is that the case with you folks?