Roman
I think overall, it sounds like a decoupling into programmatic API as one package, and then a CLI that uses said API as another package. And then also rip out...
> Why do you think exporting everything at top-level is preferred? Fewer import lines. It's not uncommon to have 5 lines importing from `projen/lib/**/*` for me. > disadvantage of using...
> Yes, that needs to be resolved. I think 1) + 2) are the same problem really and due to the missing entrypoint. Right, it _is_ about defining entry points....
~~Looks like there's an optional for this available:~~ that's for upload ... https://github.com/actions/upload-artifact#customization-if-no-files-are-found
Perhaps running inside a Dev Container is not considered to be a CI environment?
> What is the scenario here? I didn't run into any particular scenario in my own use cases, just spotted this reviewing related code. I think in the scenario you...
> I recommend you override This is what I do now. But there's still no way to distinguish between these two calls, as there are no params to the method....
@mrgrain I noticed you renamed this to add "Public API ..." Is the task named `install` considered to be private? This is the way I was hooking into it using...
To answer my own question, it does seem like this task is public: ```ts this.project.package.installTask ```
Right! I guess I was describing it in terms of methods for clarity. But really, it could be solved by having separate tasks for the initial install with `*` version,...