Rutik Wankhade - Hello! I'm on the team. Just wanted to drop by and say that we're out of beta! (and give a +1 to this idea, too)

Otherwise worked flawlessly! You may also want to note that, per current instructions, a reader will need to click into the textarea or equivalent to have the Grammarly button appear, after the clientID is specified in .env. Easter egg: There's actually a new activation EditorConfig property that displays the Grammarly button without having to press or click into a text body element. I can't post links yet because I'm a new user, but you can set the config with: activation: "immediate"

This is awesome. Thanks for writing such a comprehensive tutorial! One quick note: I was speed-reading this tutorial and following along in my terminal and came upon an error in Step 4 - Creating a Text Editor. I think it could help readers if you specify that InputTextEditor goes inside the components folder. Also, at the time of this comment, the instructions have a minor typo that leads to a bug when running locally. "create a new `component` folder" should be ... "create a new `components` folder" Thanks again! 🙂