swagger-editor 4.10.2 → 4.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +27 -19
- package/dist/swagger-editor-bundle.js +1 -1
- package/dist/swagger-editor-bundle.js.map +1 -1
- package/dist/swagger-editor-es-bundle-core.js +1 -1
- package/dist/swagger-editor-es-bundle-core.js.map +1 -1
- package/dist/swagger-editor-es-bundle.js +1 -1
- package/dist/swagger-editor.css +1 -1
- package/dist/swagger-editor.css.map +1 -1
- package/dist/swagger-editor.js +1 -1
- package/dist/swagger-editor.js.map +1 -1
- package/package.json +13 -14
package/README.md
CHANGED
|
@@ -1,15 +1,31 @@
|
|
|
1
1
|
# <img src="https://raw.githubusercontent.com/swagger-api/swagger.io/wordpress/images/assets/SWE-logo-clr.png" height="80">
|
|
2
|
-
[](http://badge.fury.io/js/swagger-editor)
|
|
3
3
|
[](https://jenkins.swagger.io/job/oss-swagger-editor-master/)
|
|
4
4
|
[](https://codeclimate.com/github/swagger-api/swagger-editor)
|
|
5
5
|
[](https://jenkins.swagger.io/view/OSS%20-%20JavaScript/job/oss-swagger-editor-master/)
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
**⏰️ Looking for the next generation version of Swagger Editor?**
|
|
8
8
|
|
|
9
|
-
|
|
10
|
-
Valid Swagger JSON descriptions can then be generated and used with the full Swagger tooling (code generation, documentation, etc).
|
|
9
|
+
SwaggerEditor is now released under two major release channels:
|
|
11
10
|
|
|
12
|
-
|
|
11
|
+
1. [SwaggerEditor@4](https://github.com/swagger-api/swagger-editor/releases?q=v4&expanded=true) - released from [master](https://github.com/swagger-api/swagger-editor/tree/master) branch and deployed at https://editor.swagger.io/
|
|
12
|
+
2. [SwaggerEditor@5](https://github.com/swagger-api/swagger-editor/releases?q=v5&expanded=true) - released from [next](https://github.com/swagger-api/swagger-editor/tree/next) branch and deployed at https://editor-next.swagger.io/
|
|
13
|
+
|
|
14
|
+
Only **SwaggerEditor@5** supports [OpenAPI 3.1.0](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md).
|
|
15
|
+
SwaggerEditor@4 will not receive OpenAPI 3.1.0 support and is considered legacy at this point.
|
|
16
|
+
The plan is to continually migrate fully to SwaggerEditor@5 and deprecate the SwaggerEditor@4 in the future.
|
|
17
|
+
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
**🕰️ Looking for the older version of Swagger Editor?** Refer to the [*2.x*](https://github.com/swagger-api/swagger-editor/tree/2.x) or [*3.x*](https://github.com/swagger-api/swagger-editor/tree/3.x) branches.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
Swagger Editor lets you edit **OpenAPI API definitions** ([OpenAPI 2.0](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md) and [OpenAPI 3.0.3](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md))
|
|
25
|
+
in JSON or YAML format inside your browser and to preview documentations in real time.
|
|
26
|
+
Valid OpenAPI definitions can then be generated and used with the full Swagger tooling (code generation, documentation, etc).
|
|
27
|
+
|
|
28
|
+
As a brand-new version, written from the ground up, there are some known issues and unimplemented features. Check out the [Known Issues](#known-issues) section for more details.
|
|
13
29
|
|
|
14
30
|
This repository publishes to two different NPM modules:
|
|
15
31
|
|
|
@@ -18,8 +34,6 @@ This repository publishes to two different NPM modules:
|
|
|
18
34
|
|
|
19
35
|
If you're building a single-page application, using `swagger-editor` is strongly recommended, since `swagger-editor-dist` is significantly larger.
|
|
20
36
|
|
|
21
|
-
For the older version of swagger-editor, refer to the [*2.x branch*](https://github.com/swagger-api/swagger-editor/tree/2.x).
|
|
22
|
-
|
|
23
37
|
## Helpful scripts
|
|
24
38
|
|
|
25
39
|
Any of the scripts below can be run by typing `npm run <script name>` in the project's root directory.
|
|
@@ -61,20 +75,14 @@ Script name | Description
|
|
|
61
75
|
|
|
62
76
|
## Running locally
|
|
63
77
|
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
- NPM >=7.x
|
|
67
|
-
|
|
68
|
-
Generally, we recommend the following guidelines from [Node.js Releases](https://nodejs.org/en/about/releases/) to only use Active LTS or Maintenance LTS releases.
|
|
78
|
+
### Prerequisites
|
|
69
79
|
|
|
70
|
-
|
|
71
|
-
- Node.js
|
|
72
|
-
- NPM >=7.10.x
|
|
73
|
-
|
|
74
|
-
Current Node.js Active LTS:
|
|
75
|
-
- Node.js 14.x
|
|
76
|
-
- NPM >=7.x.x
|
|
80
|
+
- git, any version
|
|
81
|
+
- **Node.js >=20.3.0** and **npm >=9.6.7** are the minimum required versions that this repo runs on, but we always recommend using the latest version of Node.js.
|
|
77
82
|
|
|
83
|
+
```shell
|
|
84
|
+
$ npm i --legacy-peer-deps
|
|
85
|
+
```
|
|
78
86
|
|
|
79
87
|
If you have Node.js and npm installed, you can run `npm start` to spin up a static server.
|
|
80
88
|
|