-
-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename project from mdast to remark 🎉 #113
Comments
Heads up: @ben-eb, @hughsk, @rsystem-se, @eush77, @anandthakker, @minodisk, @rhysd, @dthree, @zotplus, @tmcw, @chcokr, @denysdovhan. |
Congrats! Nice name. |
Nice! What do you suggest for plugin renaming? |
Thanks @chcokr, @ben-eb.
That would ensure no users get any deprecation notices normally, but if they are in the process of updating their dependencies, they’ll get one and hopefully rename their dependency. 😄 I know it’s quite a lot to ask, hope you all don’t mind. Furthermore, I hope the new naming will make the ecosystem better! 🎉 |
Does it mean that the preferred name prefix for util packages will be changed to just |
My congratulations! Cool name! BTW: If you know there is also a remark slideshow tool 😏 |
👍 |
@dthree @denysdovhan Yes, thanks! Cool right? And yeah, I saw the project. Luckily I got the access to npm 👍 @eush77 Yes, that’s the gist of it (see my previous comments for more info). I definitely share your concerns, but I feel that the long run will certainly be worth it. And, importantly, better now than later 👌 |
Congrats! I got it. |
I just received push-access to the
remark
project on npm (by the amazing @phated!), which means, the mdast project can step away from the hard-to-pronaunce name towards a much more easily pronounceable remark.I long coveted this name (in lieu of retext), ever since I forked into mdast more than a year ago.
Just in time for 3.0.0, but it will mean everything needs to be renamed, from mdastrc and mdastignore files, to all prefixed plug-ins.
This will also give me the opportunity to separate the AST specification from the API and CLI: mdast, similarly to NLCST for retext, will still be used as a definition for the nodes used by mdast, uhm, I mean, remark.
The text was updated successfully, but these errors were encountered: