Anton Gilgur

Still agree with all the above comments, but just wanted to note that as of v1.9 and the 2.1 file format, Compose supports bash-style inline defaults, which means optional build...

Indeed, that's why I wrote: > As @triccardi-systran noted though, you have to duplicate the default value in Dockerfile to be in docker-compose.yml as well, due to this bug and...

For WIP docs for next release vs. current/latest release, we could add a link in the `main` branch README to the latest release tag's README. E.g. "This is the documentation...

Might be necro'ing, but as a long-time user, thought I'd answer too since this wasn't closed and OP didn't quite respond. > The readme also said "These packages are highly...

I don't believe `4` is a valid package name. But PR welcome to make the error more friendly. I didn't write this code (and don't use `create`), but I believe...

> 1. Is there alignment here on how exactly this should work as a first class TSDX feature? Not exactly. The TS team itself isn't entirely supportive of `paths` being...

@jantimon you're correct if there were no additional transforms -- but a portion of this issue and the surrounding ones are around adding such a transform so that one can...

@pedroapfilho the buggy default configuration has been removed from the templates as of v0.13.3, which resolves this issue's "OR" expected behavior. I've written above in detail and with many links...

So this seems to be a bug caused by the `rollup` config's `output.file` being set to the same thing for every entry file: https://github.com/jaredpalmer/tsdx/blob/d621994f3eb21b6f686cccf7170ba541e72886c3/src/createRollupConfig.ts#L32-L33 I created a workaround-ish with `tsdx.config.js`...

So I realized there's one other fairly _big_ issue with my workaround: `tsdx` only ever outputs one CJS "entry file" (the one that splits between dev & prod builds), so...