@pirxpilot/router 1.1.0 → 2.0.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/HISTORY.md DELETED
@@ -1,217 +0,0 @@
1
-
2
- 1.1.0 / 2025-01-18
3
- ==================
4
-
5
- * simplify layer creation
6
- * remove `methods` dependency
7
- * replace run-series with await/async
8
- * allow using rawrequest with promises
9
- * minor ES6 fixes
10
- * minor improvement in Router.use
11
- * use Set to keep track of route methods
12
-
13
- 1.0.0 / 2024-12-31
14
- ==================
15
-
16
- * rename to @pirxpilot/router
17
- * relax dependecies
18
- * remove outdated and dependencies
19
- * replace `mocha` and `nyc` with built-in `node:test`
20
-
21
- 2.0.0-beta.2 / 2024-03-20
22
- =========================
23
-
24
- This incorporates all changes after 1.3.5 up to 1.3.8.
25
-
26
- * Add support for returned, rejected Promises to `router.param`
27
-
28
- 2.0.0-beta.1 / 2020-03-29
29
- =========================
30
-
31
- This incorporates all changes after 1.3.3 up to 1.3.5.
32
-
33
- * Internalize private `router.process_params` method
34
- * Remove `debug` dependency
35
- * deps: array-flatten@3.0.0
36
- * deps: parseurl@~1.3.3
37
- * deps: path-to-regexp@3.2.0
38
- - Add new `?`, `*`, and `+` parameter modifiers.
39
- - Matching group expressions are only RegExp syntax.
40
- `(*)` is no longer valid and must be written as `(.*)`, for example.
41
- - Named matching groups no longer available by position in `req.params`.
42
- `/:foo(.*)` only captures as `req.params.foo` and not available as
43
- `req.params[0]`.
44
- - Regular expressions can only be used in a matching group.
45
- `/\\d+` is no longer valid and must be written as `/(\\d+)`.
46
- - Matching groups are now literal regular expressions.
47
- `:foo` named captures can no longer be included inside a capture group.
48
- - Special `*` path segment behavior removed.
49
- `/foo/*/bar` will match a literal `*` as the middle segment.
50
- * deps: setprototypeof@1.2.0
51
-
52
- 2.0.0-alpha.1 / 2018-07-27
53
- ==========================
54
-
55
- * Add basic support for returned, rejected Promises
56
- - Rejected Promises from middleware functions `next(error)`
57
- * Drop support for Node.js below 0.10
58
- * deps: debug@3.1.0
59
- - Add `DEBUG_HIDE_DATE` environment variable
60
- - Change timer to per-namespace instead of global
61
- - Change non-TTY date format
62
- - Remove `DEBUG_FD` environment variable support
63
- - Support 256 namespace colors
64
-
65
- 1.3.8 / 2023-02-24
66
- ==================
67
-
68
- * Fix routing requests without method
69
-
70
- 1.3.7 / 2022-04-28
71
- ==================
72
-
73
- * Fix hanging on large stack of sync routes
74
-
75
- 1.3.6 / 2021-11-15
76
- ==================
77
-
78
- * Fix handling very large stacks of sync middleware
79
- * deps: safe-buffer@5.2.1
80
-
81
- 1.3.5 / 2020-03-24
82
- ==================
83
-
84
- * Fix incorrect middleware execution with unanchored `RegExp`s
85
- * perf: use plain object for internal method map
86
-
87
- 1.3.4 / 2020-01-24
88
- ==================
89
-
90
- * deps: array-flatten@3.0.0
91
- * deps: parseurl@~1.3.3
92
- * deps: setprototypeof@1.2.0
93
-
94
- 1.3.3 / 2018-07-06
95
- ==================
96
-
97
- * Fix JSDoc for `Router` constructor
98
-
99
- 1.3.2 / 2017-09-24
100
- ==================
101
-
102
- * deps: debug@2.6.9
103
- * deps: parseurl@~1.3.2
104
- - perf: reduce overhead for full URLs
105
- - perf: unroll the "fast-path" `RegExp`
106
- * deps: setprototypeof@1.1.0
107
- * deps: utils-merge@1.0.1
108
-
109
- 1.3.1 / 2017-05-19
110
- ==================
111
-
112
- * deps: debug@2.6.8
113
- - Fix `DEBUG_MAX_ARRAY_LENGTH`
114
- - deps: ms@2.0.0
115
-
116
- 1.3.0 / 2017-02-25
117
- ==================
118
-
119
- * Add `next("router")` to exit from router
120
- * Fix case where `router.use` skipped requests routes did not
121
- * Use `%o` in path debug to tell types apart
122
- * deps: setprototypeof@1.0.3
123
- * perf: add fast match path for `*` route
124
-
125
- 1.2.0 / 2017-02-17
126
- ==================
127
-
128
- * Skip routing when `req.url` is not set
129
- * deps: debug@2.6.1
130
- - Allow colors in workers
131
- - Deprecated `DEBUG_FD` environment variable set to `3` or higher
132
- - Fix error when running under React Native
133
- - Use same color for same namespace
134
- - deps: ms@0.7.2
135
-
136
- 1.1.5 / 2017-01-28
137
- ==================
138
-
139
- * deps: array-flatten@2.1.1
140
- * deps: setprototypeof@1.0.2
141
- - Fix using fallback even when native method exists
142
-
143
- 1.1.4 / 2016-01-21
144
- ==================
145
-
146
- * deps: array-flatten@2.0.0
147
- * deps: methods@~1.1.2
148
- - perf: enable strict mode
149
- * deps: parseurl@~1.3.1
150
- - perf: enable strict mode
151
-
152
- 1.1.3 / 2015-08-02
153
- ==================
154
-
155
- * Fix infinite loop condition using `mergeParams: true`
156
- * Fix inner numeric indices incorrectly altering parent `req.params`
157
- * deps: array-flatten@1.1.1
158
- - perf: enable strict mode
159
- * deps: path-to-regexp@0.1.7
160
- - Fix regression with escaped round brackets and matching groups
161
-
162
- 1.1.2 / 2015-07-06
163
- ==================
164
-
165
- * Fix hiding platform issues with `decodeURIComponent`
166
- - Only `URIError`s are a 400
167
- * Fix using `*` before params in routes
168
- * Fix using capture groups before params in routes
169
- * deps: path-to-regexp@0.1.6
170
- * perf: enable strict mode
171
- * perf: remove argument reassignments in routing
172
- * perf: skip attempting to decode zero length string
173
- * perf: use plain for loops
174
-
175
- 1.1.1 / 2015-05-25
176
- ==================
177
-
178
- * Fix issue where `next('route')` in `router.param` would incorrectly skip values
179
- * deps: array-flatten@1.1.0
180
- * deps: debug@~2.2.0
181
- - deps: ms@0.7.1
182
-
183
- 1.1.0 / 2015-04-22
184
- ==================
185
-
186
- * Use `setprototypeof` instead of `__proto__`
187
- * deps: debug@~2.1.3
188
- - Fix high intensity foreground color for bold
189
- - deps: ms@0.7.0
190
-
191
- 1.0.0 / 2015-01-13
192
- ==================
193
-
194
- * Fix crash from error within `OPTIONS` response handler
195
- * deps: array-flatten@1.0.2
196
- - Remove redundant code path
197
-
198
- 1.0.0-beta.3 / 2015-01-11
199
- =========================
200
-
201
- * Fix duplicate methods appearing in OPTIONS responses
202
- * Fix OPTIONS responses to include the HEAD method properly
203
- * Remove support for leading colon in `router.param(name, fn)`
204
- * Use `array-flatten` for flattening arrays
205
- * deps: debug@~2.1.1
206
- * deps: methods@~1.1.1
207
-
208
- 1.0.0-beta.2 / 2014-11-19
209
- =========================
210
-
211
- * Match routes iteratively to prevent stack overflows
212
-
213
- 1.0.0-beta.1 / 2014-11-16
214
- =========================
215
-
216
- * Initial release ported from Express 4.x
217
- - Altered to work without Express
package/SECURITY.md DELETED
@@ -1,24 +0,0 @@
1
- # Security Policies and Procedures
2
-
3
- ## Reporting a Bug
4
-
5
- The `router` team and community take all security bugs seriously. Thank you
6
- for improving the security of the project. We appreciate your efforts and
7
- responsible disclosure and will make every effort to acknowledge your
8
- contributions.
9
-
10
- Report security bugs by emailing the current owner(s) of `router`. This information
11
- can be found in the npm registry using the command `npm owner ls router`.
12
- If unsure or unable to get the information from the above, open an issue
13
- in the [project issue tracker](https://github.com/pillarjs/router/issues)
14
- asking for the current contact information.
15
-
16
- To ensure the timely response to your report, please ensure that the entirety
17
- of the report is contained within the email body and not solely behind a web
18
- link or an attachment.
19
-
20
- At least one owner will acknowledge your email within 48 hours, and will send a
21
- more detailed response within 48 hours indicating the next steps in handling
22
- your report. After the initial reply to your report, the owners will
23
- endeavor to keep you informed of the progress towards a fix and full
24
- announcement, and may ask for additional information or guidance.