seed-run / serverless-seed Goto Github PK

Hey there,

we're having trouble with incremental deploys. During Generating incremental deploy state, there seems to be an exception with the above error message.

What could be causing this / how can we fix this issue to finally be able to use incremental deploys? Would it make sense to share the entire build log / serverless template?
Here is an excerpt of the build log:

$ SLS_DEBUG=* serverless package --stage dev --package sls-package-output

150.69 s

Running "serverless" from node_modules

Packaging offer-tool-api for stage dev (eu-west-1)

Seed: Generating incremental deploy state...

Seed: There was a problem generating the incremental deploy state

    The "path" argument must be of type string. Received undefined

✔ Service packaged (146s)

Thanks in advance!

To reproduce:

• Install npm install serverless-seed@latest
• Run npm audit

The package.json lists [email protected], but I'm using [email protected]

Adding a yarn resolution to force 2.19.0 works, but causes an warning because this version is outside of the semver range

Hi, I like what this does and I'd like to help.

I read the blog and saw this:

It turns out, that Seed has optimized every single step, aside from the serverless package command.

Well, I have a plugin: sls-py

which optimises the packaging step to bits. Each lambda packages in parallel, where possible, now this is only for python, but still I'd like to stay compatible with all the other plugins. What will it take to do that?

I noticed some code around package Individual, but why I needed it is so that serverless itself isn't packaging, so I get to do it for serverless.

I also make use of layers. I'm wondering if its as simple as getting lambda artefact file hash on your end?