Sean Dawson

Another way to get the latest version is to: 1. Open the command palette, select "Package Control: Remove Package" and then select "ElixirSublime". 2. Open the command palette, select "Package...

It's pretty funny that this project has been around for over two years and by coincidence we stumble across the same issue within a week of each other and both...

OK I've pulled in your changes @vectorjohn I realised that the project was already using lodash so we could use `pickBy` to simplify the logic where we filter the functions....

Looks like I messed up the export syntax. After doing some more reading it turns out that the ES6 equivalent of `modules.export = xyz` is `export = xyz` We need...

@KingDarBoja Thanks I’ll give it a try. It would be good to use a versioned NPM dependency in our application rather than a git branch. Are you going to be...

Sorry that was probably badly worded :laughing: I meant its good that you published the fork to NPM, because at the moment we have an application that references this branch...

Hi @mattmeye this PR might not the best place to raise that issue. It might be better to open an issue at https://github.com/KingDarBoja/serverless-plugin-typescript/issues with some more details about how to...

I'm having the same issue which is fixed after I downgrade to 2.1.1 In my case the layer is built by an external plugin, then the layer zip file is...

After playing around with this for a bit, I have realised that the breaking change actually transforms the existing value of "service.layers[name].package.artifact" so my suggestion won't work. I'll have to...

I think we need to break the assumption that every layer has been moved by serverless-plugin-typescript and only reset the reference if the artifact was originally from the source folder....