If you're in a JavaScript project that can't handle a traditional npm module, The module also exports SwaggerUIBundle and SwaggerUIStandalonePreset, so The folder also has an index.html asset, to make it easy to serve Swagger UI like so: const express = require('express')Ĭonst pathToSwaggerUi = require('swagger-ui-dist').absolutePath() The most useful file is swagger-ui-bundle.js, which is a build of Swagger UI that includes all the code it needs to run in one file. The module's contents mirror the dist folder you see in the Git repository.

Will result in more code going across the wire. Note: we suggest using swagger-ui when your tooling makes it possible, as swagger-ui-dist The module, when imported, includes an absolutePath helper function that returns the absolute filesystem path to where the swagger-ui-dist module is installed. In contrast, swagger-ui-dist is meant for server-side projects that need assets to serve to clients.

See the Webpack Getting Started sample for details. Here's an example: import SwaggerUI from 'swagger-ui' Its main file exports Swagger UI's main function, and the module also includes a namespaced stylesheet at swagger-ui/dist/swagger-ui.css. Swagger-ui is meant for consumption by JavaScript web projects that include module bundlers, such as Webpack, Browserify, and Rollup. We publish two modules to npm: swagger-ui and swagger-ui-dist. Installation Distribution channels NPM Registry

Swagger editor docker start