You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For ES6 npm users, run 'npm install --save url-knife' on console.
25
-
(Node v18.20.4)
29
+
(**Requred Node v18.20.4**)
26
30
27
31
```html
28
32
import Pattern from 'url-knife';
@@ -39,14 +43,13 @@ import Pattern from 'url-knife';
39
43
40
44
41
45
#### Chapter 1. Normalize or parse one URL
42
-
The following two methods should be used for only one url, not for multiple ones in texts.
43
-
(for multiple ones, refer to Chapter 2 & 4)
46
+
The following two methods should be used for processing a single URL, not for multiple URLs within a text.
47
+
(For handling multiple URLs, refer to Chapters 2 and 4.)
44
48
45
49
##### normalizeUrl vs parseUrl
46
-
If you want to parse a normal url with no typos, it is safe to use <b>parseUrl</b>. However, <b>normalizeUrl</b> is for
47
-
parsing urls with possible human errors.
50
+
If you need to parse a standard URL without any typos, it is safe to use ``parseUrl``. However, ``normalizeUrl`` is designed to handle URLs that may contain human errors.
48
51
49
-
*##### normalizeUrl
52
+
*##### Run ``normalizeUrl``
50
53
51
54
```javascript
52
55
/**
@@ -58,7 +61,7 @@ var sample2 = Pattern.UrlArea.normalizeUrl("'://abc.jppp:9091 /park/noon'")
58
61
var sample3 =Pattern.UrlArea.normalizeUrl("ss hd : /university,.acd. ;jpkp: 9091/adc??abc=.com")
0 commit comments