Tim Stackhouse

:+1: I'm running into this issue too with reorganizing my library

It's a step in the right direction, though I was doing some more testing and found another issue in the upload artifacts step when not packaging individually: https://github.com/serverless/serverless/blob/master/lib/plugins/aws/deploy/lib/uploadArtifacts.js#L104-L116 That usage...

The opposite actually, at least in my experience. Packaging individually works because it goes inside both if statements in that code in uploadArtifacts.js. Not packaging individually only goes into the...

> `Commenting the return on line 115 allows the if statement to be exited and the deploy works correctly.` in which file? Sorry, I was on my phone and getting...

I'm investigating updating to 2.x and at least upon first impressions, the way this plugin handling initializing serverless, if we use an SSM reference in our `serverless.yml`, the framework attempts...

Researching a bit more, it almost seems like something is causing the AWS plugins to not load at all: ``` Serverless: Load command param:list Serverless: Load command studio Serverless: Configuration...

I've been able to get back into this a bi, trying to update to 1.1.0 and serverless 2 in my project, and this bug is related to a slightly different...

I've actually tracked down an easy potential fix for this, by changing the code here: https://github.com/flowaccount/nx-plugins/blob/master/libs/nx-serverless/src/utils/serverless.ts#L126-L132 from: ``` if ( deployOptions && deployOptions.function && deployOptions.function != '' ) { serverlessConfig.servicePath...

That looks like it could be related to changes in webpack 5’s exports. I’ve not touched it yet, I may be able to dig around tomorrow, but at least in...

I'd need to experiment with that a bit, it's an interesting thought. We had used the `compile` executor at one point I believe, but missing out on all the bundling...