This is a follow-up to a previous topic I can no longer reply to. My question in short: If we can’t use private packages, how do people collaborate on packages? The long version:
- I have an app that uses some third-party packages.
- What often happens is that I want to fix a bug or add a feature to those packages.
- In other developer ecosystems I would fork the package, make changes, try them in my app using the fork and then submit the changes back upstream to the original forked package.
- The try them in my app part is crucial, the changes are seldom so simple as to make them without testing in a live app.
- But since we can’t use private packages in Elm, there’s no easy way to test those changes in my app, is it? (That’s the point of the previous thread I have linked to.)
- Some changes can be tested using unit tests, but often that’s not enough, maybe I need to verify that the changes work against some backend service.
- In other developer ecosystems I could write an automated end-to-end test to verify the changes against a live service. In Elm it doesn’t seem feasible to use side effects in tests?
In the end, the current Elm ecosystem makes it harder for me to collaborate effectively on packages. Or am I missing something? What’s your workflow?