Gathering detailed insights and metrics for spectacle-docs-ets
Gathering detailed insights and metrics for spectacle-docs-ets
Gathering detailed insights and metrics for spectacle-docs-ets
Gathering detailed insights and metrics for spectacle-docs-ets
Beautiful static documentation generator for OpenAPI/Swagger 2.0
npm install spectacle-docs-ets
Typescript
Module System
Node Version
NPM Version
28.4
Supply Chain
62.7
Quality
62
Maintenance
25
Vulnerability
50
License
JavaScript (38.5%)
CSS (38.05%)
HTML (22.53%)
Shell (0.79%)
Dockerfile (0.12%)
Total Downloads
8,480
Last Day
2
Last Week
16
Last Month
76
Last Year
376
1 Stars
324 Commits
5 Watching
4 Branches
Latest Version
0.8.26
Package Id
spectacle-docs-ets@0.8.26
Size
2.16 MB
NPM Version
5.3.0
Node Version
7.10.0
Cumulative downloads
Total Downloads
Last day
-33.3%
2
Compared to previous day
Last week
-67.3%
16
Compared to previous week
Last month
76.7%
76
Compared to previous month
Last year
-23.4%
376
Compared to previous year
41
1
The gentleman at REST
Spectacle generates beautiful static HTML5 documentation from OpenAPI/Swagger 2.0 API specifications.
The goal of Spectacle is help you "save time and look good" by providing an extensible platform for auto generating your REST API docs. The default layout is a three column single page, similar to those employed by Stripe and Intercom.
See a demo of Spectacle in action here: http://cheesestore.github.io
<body>
for convenient integration into your existing website.Simply install Spectacle from npm
like so:
1npm install -g spectacle-docs-ets
Next pass your swagger.json
document use the CLI to generate your documentation.
1spectacle -d your_swagger_api.json 2 3# Or use the cheese.json example to test it out 4# spectacle -d -l test/fixtures/cheese.png test/fixtures/cheese.json
Your generated documentation will be located in the public
directory by default. You can either copy the generated HTML to your web server, or view your docs by pointing your browser to http://localhost:4400/.
A basic Docker script is included that allows Spectacle to be run from the inside, not outside. It's useful, for instance, in a Gitlab CI pipeline. Thanks @alexeiaguiar.
How to use it: docker run -it sourcey/spectacle /bin/sh
The basic CLI options are detailed below:
1$ spectacle -h 2 3 Usage: spectacle spactacle [options] <specfile> 4 5 Options: 6 7 -h, --help output usage information 8 -V, --version output the version number 9 -C, --disable-css omit CSS generation (default: false) 10 -J, --disable-js omit JavaScript generation (default: false) 11 -e, --embeddable omit the HTML <body/> and generate the documentation content only (default: false) 12 -d, --development-mode start HTTP server with the file watcher and live reload (default: false) 13 -s, --start-server start the HTTP server without any development features 14 -p, --port <dir> the port number for the HTTP server to listen on (default: 4400) 15 -t, --target-dir <dir> the target build directory (default: public) 16 -f, --target-file <file> the target build HTML file (default: index.html) 17 -a, --app-dir <dir> the application source directory (default: app) 18 -l, --logo-file <file> specify a custom logo file (default: null) 19 -c, --config-file <file> specify a custom configuration file (default: app/lib/config.js)
Most options are self explanatory, but the following options warrant some further explanation:
--development-mode -d
: This option starts a development server with a file watcher and live reload, and will automatically regenerate your docs when any of your spec or app files change.
--start-server -s
: This option starts a production server without any development options enabled that serves the contents of your --target-dir
.
--embeddable -e
: This option lets you build a minimal version of the documentation without the HTML <body>
tags, so you can embed Spectacle into your own website template. More info on custom builds here.
--app-dir -a
: This option overrides the default directory which contains all the Handlebars templates, SCSS, and JavaScript source files. This option is useful for development because you can copy the contents of app
to a remote location or a separate repo for custom builds.
--target-dir -t
: This option specifies where the generated documentation HTML files will be output.
Default ETS task, equal to spectacle -l ./logo.png ./spec.yaml -t ./web/
1npm run ets
The best option for building your own custom functionality into Spectacle is to fork Spectacle on GitHub, and make your own modifications in source. This way you can keep up to date by merging changes from the master
branch, and your can also contribute your updates back to master
by creating a Pull Request if you think they improve Spectacle somehow.
To fork Spectacle go to https://github.com/sourcey/spectacle
, and press the 'Fork' button. Now you can git clone git@github.com:<yourname>/spectacle.git
to make your own changes.
Alternatively, you can just copy the contents of app
from the main repo which contains all the source files such as templates, stylesheets and JavaScripts. Now just pass the path to your custom app
path to the CLI like so: spectacle -a /path/to/your/app your_swagger_api.json
Using an API spec to generate your docs has a number of great advantages, such as:
As developer we're always looking for ways to improve and optimize our workflow, and documentation is just the beginning. With a well written Swagger you can automate and generate many parts of your API system, such as:
For a list of open source Swagger based libraries in many languages check here: http://swagger.io/open-source-integrations/
More info is available on the Spectacle homepage.
Please use the GitHub issue tracker if you have any ideas or bugs to report.
All contributions are welcome.
Good luck and enjoy Spectacle!
No vulnerabilities found.
No security vulnerabilities found.