Skip to content

Conversation

@alastairmccormack
Copy link

@alastairmccormack alastairmccormack commented Nov 3, 2019

Without specifying package.artifact, Serverless continues to use its own package

Without specifying `package.artifact`, Serverless continues to its own package
@philip-ulrich
Copy link

This PR helped me debug an issue i was having identical to yours. I think it's better to just add the new

package:
  individually: true

then include the artifact in the function package section - especially with the note that since 1.18 the package individually portion is needed according to the readme.

Sadly though this project seems abandoned so no one will likely every merge either change in. Hope it continues to run without issue and no updates. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants