Open natebosch opened 4 years ago
Unfortunately the CSS team's staffing is such that we don't really have the ability to maintain upstream components. However, we do depend heavily on the ability to run tests on Node, so hopefully we can find a way to make this work that won't break us.
We want to move away from the Dart team needing expertise on node for our first party tools. One of the biggest dependencies we have on node today is the platform in this package. Ideally we'd like the node platform to be supported outside of the Dart team.
We are blocked by the fact that removing node support is breaking, and we don't have a supported migration path for building back that support outside of the package.
One option might be to finish fleshing out
test_core
into a stable API and make it possible to define external "runners". With what we have today that might mean some amount of duplication of other stuff intest
. Givenflutter_test
and the hacks that other folks are already doing withsrc/
imports, this is probably work that we do want to happen at some point anyway.I think we probably want to steer clear of runtime code injection using isolates etc - the entry point would likely not be
pub run test
- it may instead be something likepub run node_test
.cc @nex3 for thoughts on how this might look, and whether the Sass team is interested in owned the node platform runner.