thomas michael wallace

Although I do use this in production, it's a bit of a hack. Can I suggest we take a leaf out of webpack's book and support serverless.config.js, which exports a...

Interesting- I don't think that approach would have ever occured to me. The splatting bits works up to a point (that's what we do with the concat; as the common...

I discussed the difficulties that the use of yaml was bringing in compared to other frameworks I also use to deliver apps (specifically I had webpack's in mind). I then...

Indeed- while I was thinking through how I would use a severless.js to replace our current hack of `cat serverless.${AWS_PROVIDER}.yml serverless.common.yml serverless.project.yml > serverless.yml` I was thinking that the one...

@simlu That looks interesting- although I still think that sticking to straight yaml and json with the option to use javascript for more complex scenarios makes the most sense: 1)...

Personally I think you're overstating the complexity of changing from a yml to javascript. I mean, at it's simplest you're just exporting an object with the same keys and the...

@simonbuchan fair point, and I also agree with @erikerikson - there's going to be people, like me, who feel more comfortable in javascript and want to use it, and probably...

n.b. I've added a branch to my #225 PR that includes the built version of mocha-webpack with the fix in. So if you want a working version, you can temporarily...

This is happening to me as well, with a simpler: `mocha-webpack \"test/**/*.spec.js\"`. Same version of mocha-webpack and webpack, though. I don't remember this being a problem across the last year...

And another datapoint: Having just moved to GitHub, we're looking to tidy up our Releases. We have 239 tags/releases on our private repo. Running `yarn gren release --data-source=commits` results in...