@furystack/rest
Advanced tools
@furystack/rest - npm Package Compare versions
Comparing version 7.0.3 to 7.0.4
@@ -10,7 +10,2 @@ # Change Log | ||
| ### [3.1.7](https://github.com/furystack/furystack/compare/@furystack/rest@3.1.6...@furystack/rest@3.1.7) (2022-02-02) | ||
@@ -20,7 +15,2 @@ | ||
| ### [3.1.6](https://github.com/furystack/furystack/compare/@furystack/rest@3.1.4...@furystack/rest@3.1.6) (2022-01-10) | ||
@@ -30,7 +20,2 @@ | ||
| ### [3.1.5](https://github.com/furystack/furystack/compare/@furystack/rest@3.1.4...@furystack/rest@3.1.5) (2022-01-10) | ||
@@ -40,7 +25,2 @@ | ||
| ### [3.1.4](https://github.com/furystack/furystack/compare/@furystack/rest@3.1.3...@furystack/rest@3.1.4) (2021-12-20) | ||
@@ -50,7 +30,2 @@ | ||
| ### [3.1.3](https://github.com/furystack/furystack/compare/@furystack/rest@3.1.2...@furystack/rest@3.1.3) (2021-12-08) | ||
@@ -60,7 +35,2 @@ | ||
| ### [3.1.2](https://github.com/furystack/furystack/compare/@furystack/rest@3.1.1...@furystack/rest@3.1.2) (2021-11-30) | ||
@@ -70,7 +40,2 @@ | ||
| ### [3.1.1](https://github.com/furystack/furystack/compare/@furystack/rest@3.1.0...@furystack/rest@3.1.1) (2021-11-29) | ||
@@ -80,17 +45,8 @@ | ||
| ## [3.1.0](https://github.com/furystack/furystack/compare/@furystack/rest@3.0.21...@furystack/rest@3.1.0) (2021-11-19) | ||
| ### 🚀 What's new | ||
| * **@furystack/rest:** Extended allowed HTTP methods with HEAD, CONNECT and TRACE ([85b91f2](https://github.com/furystack/furystack/commit/85b91f2254a7459d4cb121caeccec792880467fa)) | ||
| - **@furystack/rest:** Extended allowed HTTP methods with HEAD, CONNECT and TRACE ([85b91f2](https://github.com/furystack/furystack/commit/85b91f2254a7459d4cb121caeccec792880467fa)) | ||
| ### [3.0.21](https://github.com/furystack/furystack/compare/@furystack/rest@3.0.20...@furystack/rest@3.0.21) (2021-11-09) | ||
@@ -100,7 +56,2 @@ | ||
| ### [3.0.20](https://github.com/furystack/furystack/compare/@furystack/rest@3.0.19...@furystack/rest@3.0.20) (2021-10-15) | ||
@@ -110,7 +61,2 @@ | ||
| ### [3.0.19](https://github.com/furystack/furystack/compare/@furystack/rest@3.0.18...@furystack/rest@3.0.19) (2021-10-05) | ||
@@ -120,7 +66,2 @@ | ||
| ### [3.0.18](https://github.com/furystack/furystack/compare/@furystack/rest@3.0.17...@furystack/rest@3.0.18) (2021-09-16) | ||
@@ -130,7 +71,2 @@ | ||
| ### [3.0.17](https://github.com/furystack/furystack/compare/@furystack/rest@3.0.16...@furystack/rest@3.0.17) (2021-08-27) | ||
@@ -140,7 +76,2 @@ | ||
| ### [3.0.16](https://github.com/furystack/furystack/compare/@furystack/rest@3.0.15...@furystack/rest@3.0.16) (2021-08-19) | ||
@@ -150,7 +81,2 @@ | ||
| ### [3.0.15](https://github.com/furystack/furystack/compare/@furystack/rest@1.3.2...@furystack/rest@3.0.15) (2021-08-19) | ||
@@ -160,9 +86,4 @@ | ||
| ### [3.0.14](https://github.com/furystack/furystack/compare/@furystack/rest@1.3.2...@furystack/rest@3.0.14) (2021-07-30) | ||
| **Note:** Version bump only for package @furystack/rest |
| { | ||
| "name": "@furystack/rest", | ||
| "version": "7.0.3", | ||
| "version": "7.0.4", | ||
| "description": "Generic REST package", | ||
@@ -40,7 +40,7 @@ "type": "module", | ||
| "dependencies": { | ||
| "@furystack/core": "^14.0.3", | ||
| "@furystack/inject": "^11.0.2" | ||
| "@furystack/core": "^14.0.4", | ||
| "@furystack/inject": "^11.0.3" | ||
| }, | ||
| "devDependencies": { | ||
| "@types/node": "^20.12.11", | ||
| "@types/node": "^20.12.13", | ||
| "typescript": "^5.4.5", | ||
@@ -47,0 +47,0 @@ "vitest": "^1.6.0" |
@@ -8,2 +8,3 @@ # REST | ||
| An ideal way to implement REST APIs in FuryStack is the following: | ||
| 1. Design the REST API - Create an interface that defines all endpoints, all requirements and all possible return values (~_this package_) You can place in a common module in a Monorepo that can be accessed both with the Backend and Frontend logic to share the API definition | ||
@@ -17,2 +18,2 @@ 1. Implement the defined API endpoint using the interface on the backend service (~@furystack/rest-service) | ||
| 1. Your service and client will be tightly coupled. However it can be beneficial if this is intentional but it doesn't fin in all REST API scenarios | ||
| 1. Validation doesn't come with type definitions by default - Type safety is compile-time only | ||
| 1. Validation doesn't come with type definitions by default - Type safety is compile-time only |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Number of lines in readme file
- increased by12.5%
18
Worsened metrics
- Total package byte prevSize
- decreased by-0.14%
55961
Dependency changes
Updated@furystack/core@^14.0.4
Updated@furystack/inject@^11.0.3