I'm no longer actively maintaining this project. If you are interested supporting it - ping me on twitter. The only thing that I will ask you is to not change the API drastically. If you are planning on doing that - better start a brand new project.
If you want me to transfer you only the name on npm, I'd be happy to only if the project does not have any downloads on npm lately. In case it's being downloaded, there are people that depend on it and might step up and start maintaining, so I will not transfer it to you, regardless if you want to release a new major version etc.
If you have any other questions, let me know.
jsmd ensures that you will never have outdated and non-working code in your README files.
Usage: jsmd <path> Options: --show display the compiled JS after execution --help display this help message --version display the version number
Just write your README files in GitHub Flavored Markdown as usual. The only thing that you have to add is the actual assertions. So here is a small example that will hopefully illustrate how assertions look:
var fs = ;fs;
In this simple example we expect that the type of
err is equal to 'object'.
As simple as that.
In order to verify if everything works properly just supply the desired file to jsmd and it will verify it for you:
$ jsmd README.md
See the examples for more info.
Sometimes you don't want to put helper code into your readme file, but it's necessary in order to perform the tests. In this case, you can simply add special html comments which jsmd will extract and put inside the compiled file.
<!-- js var server = require('express'); server(); -->
That way, GitHub won't visualize the comment but jsmd will be able to parse it.
jsmd has very simple flow, that looks like this:
Math.min(1, 2) // => 1
$ npm install jsmd -g
$ npm test
$ npm run-script coverage
Special thanks to:
(The MIT License)
Copyright (c) 2013 Veselin Todorov firstname.lastname@example.org
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.