Possible to split into packages so that the non-flutter parts can be used in a non-flutter project? about webcrypto.dart

[matehat]

I want point out that not wanting to tackle this now is an unfortunate decision. Most of the ecosystem seem to solve that problem in the manner proposed by me and @serverwentdown, and not solving it at all will lead to people forking your library and publishing a dart-only implementation, thereby splitting the ecosystem.

[jonasfj]

I agree this is a problem.

For this package I'm working on improving the interface / documentation / tests, etc. I know that there is work in progress for shipping Dart "plugins" too.

In the mean time, I'd suggest just vendoring with something like:
https://pub.dev/packages/vendor

Then you don't need to fork, and you can just copy the files you need and use it. It's an ugly hack, but solves your immediate issue.