Eduardo Bouças

@canac That is expected behaviour. One of the `src` directories comes from your project, whereas the other is introduced by `zip-it-and-ship-it` — they just happen to have the same name....

Hi @Lucaslpena, I'm really sorry about the late response on this issue. If you're still experiencing the problem, could you try opting in to the new esbuild bundler? You can...

> @eduardoboucas do you think this is a good candidate for `good first issue`? Maybe we can get a contribution for this. > Is this the right place to start?...

Hi @mjswensen! We're in the processing of rolling out a change that will address this issue, without you having to do any of the workarounds you described. The change is...

I believe the issue in question only applies to the test suite itself, in the sense that we're using a different method for unzipping the archives to assert their contents....

Hi @Saeris! Thanks for this PR. > Because esbuild does not support user configuration files, nor does zip-it-and-ship-it or netlify-cli provide a way for users to customize the esbuild configuration,...

> If esbuild is how Netlify wants to go forward with bundling/compiling lambda functions then I think you're going to run into this problem often or you'll end up limiting...

That's true, but it requires the "inner component" to be a partial and therefore not arbitrary dynamic content, which almost defeats the purpose. Being able to pass any block of...

> Alright, what you want is a custom Dust helper (...) I don't think helpers are the answer. With that pattern, I would end up no partials at all and...

Any updates on this? Thanks!