Jonas Finnemann Jensen
Jonas Finnemann Jensen
> Native compilation adds some restrictions (on things like Isolates or mirrors) and so could break some binaries if we do it everywhere. Exactly, what's the motivation for using this...
Does that make `pub` sort of a _build system_. I'm not saying we shouldn't, just that maybe we should think about all the things that will follow and do something...
Note: This would have implications that makes it harder SLSA attestations with automated publishing as we'd probably want to run such publish-hook in a non-networked environment.
> I don't think @jonasfj would approve modifying the pub cache. Yeah, modifying `$PUB_CACHE` is a big no no. But also you really want your build-dependencies covered by `pubspec.lock`. Otherwise,...
In particular, I can imagine that given how packages can pass meta-data and build assets between each other, it could cause problems if `foo` depends on `bar`, and both have...
> So if we introduce private_dependencies, we need to document clearly that you cannot add packages to private_dependencies when you rely on serialized formats You can rely on private_dependencies, you...
@mosuem Why would you pin dependencies?
Okay, I understood it as pinning a dependency to the same version. In the case of protobuf (or similar), I would suspect that there easily is a runtime component to...
Maybe a warning is too strong... there are legitimate reasons to not include a default binary. So maybe it should just be a hint.
We could limit to only warn if `bin/*.dart` exists and there is no `bin/.dart`.