-
-
Sebastian Retweeted Sebastian
Sebastian added,
SebastianVerified account @sebmckWorking on config validation for a tool I'm working on with nice error messages, references to source code, consumption via a type-safe API, parses JSON with comments, and allows manipulation and reserialisation with original source comments pic.twitter.com/D3AWSPtLPvShow this thread1 reply 0 retweets 5 likesShow this thread -
Sebastian Retweeted Sebastian
Sebastian added,
1 reply 0 retweets 7 likesShow this thread -
Sebastian Retweeted Sebastian
Sebastian added,
SebastianVerified account @sebmckContinuing the trend of nice error messages. Validation of package.json including parsing of semver ranges/versions with frames pointing to the exact source location in JSON. A combination of a custom JSON parser, and then chaining it with a custom semver parser with an offset. pic.twitter.com/dQC3U5JEI9Show this thread1 reply 0 retweets 3 likesShow this thread -
Sebastian Retweeted Sebastian
Sebastian added,
1 reply 0 retweets 4 likesShow this thread -
Sebastian Retweeted Sebastian
Sebastian added,
2 replies 0 retweets 12 likesShow this thread -
All of these tweets seem fairly vague alone, but in aggregate they tell a larger story. This will be open source. I don't know when. I am the only one working on it (hopefully not for long). Happy to answer any questions.
9 replies 4 retweets 106 likesShow this thread -
Replying to @sebmck
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.
2 replies 0 retweets 3 likes -
Replying to @mjackson
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.
2 replies 0 retweets 6 likes -
Replying to @sebmck
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?
2 replies 0 retweets 0 likes
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.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Replying to @sebmck
Gotcha. Ya I've always looked at the package.json spec and seen a few fields that never actually lived up to their potential, docs being one of them. Good to see you actually making use of it
0 replies 0 retweets 3 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
he/him 