Reason # 467 to not rely on software produced by 37 Signals:
https://github.com/hotwired/turbo/issues/1456
My only surprise is that David Rails didn't just post a picture of the fuck you slide and actually wrote a response
Reason # 467 to not rely on software produced by 37 Signals:
https://github.com/hotwired/turbo/issues/1456
My only surprise is that David Rails didn't just post a picture of the fuck you slide and actually wrote a response
@davetron5000 Literally last week, I was updating dependencies and ran headfirst into this gem's and accompanying Node package's poor maintenance.
The GitHub releases link to diffs which are utterly useless. Code just… appears? A close look at those diffs also shows mismatched version strings between the Git tag and the code itself.
Like… from whence do these changes land in the project?
@jgarber @davetron5000 OH I can tell you this!
So basically they release a new version to NPM here: https://github.com/hotwired/turbo
and then they go to the gem here: https://github.com/hotwired/turbo-rails/blob/main/package.json#L22-L23
and then they update the `package.json` to contain the new version of `@hotwired/turbo` and then they run the build through rollup and commit the new changes from running the rollup build 🙃
so the diff on `@hotwired/turbo-rails` is basically the result of running Rollup on `@hotwired/turbo`
@konnorrogers @davetron5000 oh good grief 🤦🏻♂️
(Thank you for the links, too! 😅)