fix: "dart_frog build" doesn't handle packages with relative paths

[jtmcdole]

Description

When running dart_frog build, it just copies the pubspec.yaml without any manipulation. Relative paths end up failing. My current workaround is to just have a step that updates relative paths when making new builds.

Steps To Reproduce

Have a pubspec with relative deps:

dependencies:
  shared:
    path: ../shared

Expected Behavior

dependencies:
  shared:
    path: ../../shared

Additional Context

I haven't tested this with melos / pub workspaces, but I suspect its also broken as you have to use bootstraping every time you build.

[felangel]

Can you share the output of dart_frog --version and the operating system you're using? Dart Frog should automatically bundle all external path dependencies as part of the production build and generate a pubspec_overrides.yaml. We also did add support for pub workspaces a few months back so those use cases should all be supported. I'm personally working on multiple projects atm that use Dart Frog and pub workspaces with no issues fwiw.

It would be super helpful if you could provide a link to a minimal reproduction sample that any of us can clone and run, thanks!

[felangel]

@jtmcdole I just tried to reproduce and was unable to so any additional information you can share would be super helpful, thanks!

Can you clone the following project and test if it works for you?
https://github.com/felangel/dart_frog_relative_path_dependency

cd server
dart_frog build
dart build/bin/server.dart

Also in case it's helpful we have a Discord Server 😄