David Sherret

Best solution IMO was actually to create a release.yml file, which will automate bumping the version in Cargo.toml and tagging the repo.

@declanvong sorry for my huge delay on this. I just rebased this (can't push to your branch because I don't have permission) and tried it out. It seems much better!...

Yeah, I failed at fixing the commit author 😅 (I've given up because it will be resolved once squash merged) Edit: Fixed.

@IWANABETHATGUY definitely. Thanks a lot!

Hey @syrusakbary, sorry I was away and then I've been busy since I got back. I'm not sure how dprint could take advantage of this mostly because I don't understand...

@adamchainz Interesting! I'm not familiar with this tool. I'm looking at the documentation... does it clone the entire repo or just grab out the `.pre-commit-hooks.yaml` file? If it clones the...

Hey @matklad, really interesting post and it's neat to see where rust-analyzer is going. One of my coworkers was talking about it the other day commenting on how much he...

Sorry, been pretty busy working on a few things especially with the TS 3.8 release coming up. If either of you are ever in Toronto then let me know as...

@zhmushan see this document https://github.com/dprint/dprint/blob/main/docs/wasm-plugin-development.md Let me know if there are any details missing.

With the case of dprint-plugin-markdown, it needs to be compiled with the wasm feature: ``` cargo build --target wasm32-unknown-unknown --release --features "wasm" ``` https://github.com/dprint/dprint-plugin-markdown/blob/main/.github/workflows/ci.yml That will add the wasm exports....