Closed Strydom closed 4 years ago
I would guess that the builder is null because the Protobuf library isn't working properly, or there is no Protobuf being included in the distribution. I'm afraid I don't know enough about how the typescript binary might be created to comment further.
When i run the build I do get this warning:
WARNING in ./node_modules/bytebuffer/dist/bytebuffer-node.js
Module not found: Error: Can't resolve 'memcpy' in '/Users/chstrydom/Documents/GitHub/blacksmith-foundry-dynamo-listener/node_modules/bytebuffer/dist'
@ ./node_modules/bytebuffer/dist/bytebuffer-node.js
@ ./node_modules/protobufjs/dist/protobuf.js
@ ./node_modules/aws-kinesis-agg/lib/common.js
@ ./node_modules/aws-kinesis-agg/lib/kpl-deagg.js
@ ./node_modules/aws-kinesis-agg/index.js
@ ./node_modules/blacksmith-kinesis-mapper/lib/deaggregate.js
@ ./node_modules/blacksmith-kinesis-mapper/lib/KinesisMapper.js
@ ./src/index.ts
Can you let me know when the new version is published please?
Could you push a hotfix please? We forgot to update this https://github.com/awslabs/kinesis-aggregation/blob/master/node/package.json#L30 so the .json version hasn't been published
Hello,
I'm having issues using this library in a Typescript project that is being webpacked. I'm able to run the code in the TS package (
blacksmith-kinesis-mapper
) where i use theaws-kinesis-agg
library and when I run my integration tests before packaging the Node Lambda (blacksmith-foundry-dynamo-listener
) that pulls in the TS package.The issue arrises when I package the lambda code up using webpack. I get the error in AWS and when i run the code locally with
lambda-local
.The stack trace seems to point to https://github.com/awslabs/kinesis-aggregation/blob/master/node/lib/common.js#L43
I'm not sure If it's an issue with my project or if you need to do something to prevent webpack from treeshaking needed files etc?