You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we are starting to get more libs in the ecosystem, it would be nice to have a CI build that compiles all the libs at their latest versions whenever something changes.
We could setup a project like relude-ci or relude-packages, and npm install all the libraries we want (including any community libs), and then try to setup some automated workflow to submit pull requests for library updates, merge the pull requests to update the package.json, and run the CI build.
At one point we talked about seeing if the package-set concept would work (using purescript spago), but I don't think we want to take on that additional dependency at this time. I think we could get by with a simple repo that installs the versions and runs some builds.
The text was updated successfully, but these errors were encountered:
Since we are starting to get more libs in the ecosystem, it would be nice to have a CI build that compiles all the libs at their latest versions whenever something changes.
We could setup a project like
relude-ci
orrelude-packages
, andnpm install
all the libraries we want (including any community libs), and then try to setup some automated workflow to submit pull requests for library updates, merge the pull requests to update the package.json, and run the CI build.At one point we talked about seeing if the package-set concept would work (using purescript spago), but I don't think we want to take on that additional dependency at this time. I think we could get by with a simple repo that installs the versions and runs some builds.
The text was updated successfully, but these errors were encountered: