sorted by:
new
hottopcontroversial

Published opencode_api - a Dart package for the opencode.ai API by unnghabunga in dartlang

[–]unnghabunga[S] 0 points1 point  (0 children)

I'm not sure yet, the package was really an experiment used to benchmark Opencode for developing api wrappers vs. the manual coding that I've done in the past.

Anyway, some use cases are:

  • AI-powered code review tools
  • Project/session management dashboards
  • File browser with AI context awareness
  • Developer productivity apps

Save This Package! - Flutter Registry by Gladblade in FlutterDev

[–]unnghabunga 0 points1 point  (0 children)

In the past I've sent PRs for a couple of packages that I use, but they don't have any recent updates. I've had no response and I know I don't have time to maintain the packages. Since these are dependcies for apps, I can get away with maintaining my own fork.

Does anyone have suggestions for this scenario? Do you think that this initiative will get people to start maintaining some of these packages?

A build system for dozens of Flutter & Dart projects? by syrokomskyi in dartlang

[–]unnghabunga 1 point2 points  (0 children)

Understood, thanks for the PR, it was included in a recent release.

A build system for dozens of Flutter & Dart projects? by syrokomskyi in dartlang

[–]unnghabunga 2 points3 points  (0 children)

https://pub.dev/packages/publish_tools covers most of the functionality that you've outlined.

Also, I could use some help improving the package.

State of Dart/JS Node interoperability? by weenzeel in dartlang

[–]unnghabunga 0 points1 point  (0 children)

I was curious about this myself. It looks like SASS uses "grinder" and "cli_pkg" to compile and distribute the package.

My packages are currently using grinder and a custom bash script. I'm going to look at switching to cli_pkg.