he/him 
Show this thread
-
Are you planning to include any tool for API documentation? I've always thought it'd be cool if documentation were built into my package manager, e.g. `rome docs react` might let me browse the docs for a package right there in the terminal.
npm already has a solution for that, man pages. It's a specific field in package.json. It could be a lot easier to automatically build and consume them though. Using existing standards is preferred, I wouldn't want to bifurcate the ecosystem unless it was substantially worth it.
-
-
Generating HTML/JSON documentation from a JS file, with inferred types and reading comments would be dope though. It would definitely be possible, I will likely build it anyway just to generate docs for Rome.
-
If you generate man pages, there's already existing tools to convert man pages to HTML.
- 2 more replies
New conversation -
-
-
I don't understand. npm already has a solution for installing packages too, but you're building that into rome, right? How do you choose what to include and what to ignore?
-
Compatibility and integration with the ecosystem. Consolidate around standards, not tools. Using Rome shouldn't make it more difficult for others to use X tool of choice. Consumers should be able to reap benefits without actually using it.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.