xml-twig 1.3.4 → 1.3.6
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 +2 -2
- package/package.json +1 -1
- package/twig.js +3 -1
package/README.md
CHANGED
|
@@ -33,7 +33,7 @@ npm install node-expat
|
|
|
33
33
|
npm install saxophone
|
|
34
34
|
|
|
35
35
|
```
|
|
36
|
-
In my tests I parsed a 900 MB big XML file, the `node-expat` is faster than `sax` (node-expat: around 2:
|
|
36
|
+
In my tests I parsed a 900 MB big XML file, the `node-expat` is faster than `sax` (node-expat: around 2:30 Minutes, sax: around 3:40 Minutes). However, you may run into problems when you try to install the `node-expat` parser. That's the reason why `node-expat` parser is not installed automatically. `saxophone` is even a little faster (around 2:10 Minutes) than `node-expat`, however `saxophone` lacks some functions and is not fully compliant to XML standards.
|
|
37
37
|
|
|
38
38
|
## How to use it
|
|
39
39
|
|
|
@@ -322,7 +322,7 @@ You can specify condition on above methods. You can filter elements by following
|
|
|
322
322
|
|
|
323
323
|
For details see [ElementCondition](./doc/twig.md#ElementCondition).
|
|
324
324
|
|
|
325
|
-
For methods which return a **Twig[]** array, a call like `elt.
|
|
325
|
+
For methods which return a **Twig[]** array, a call like `elt.sibling("book")` is equal to `elt.sibling().filter( x => x.name === "book" )`
|
|
326
326
|
|
|
327
327
|
For methods which return a single **Twig** element (e.g. `elt.next("book")`) the method is executed in a loop till a `<book>` element is found.
|
|
328
328
|
|
package/package.json
CHANGED
package/twig.js
CHANGED
|
@@ -29,7 +29,9 @@ let current;
|
|
|
29
29
|
|
|
30
30
|
/**
|
|
31
31
|
* @external libxmljs
|
|
32
|
-
*
|
|
32
|
+
* Though module looks promising, it is not implemented, because it does not support Streams.
|
|
33
|
+
* According to {@link https://github.com/libxmljs/libxmljs/issues/390|Stream Support} it was requested in 2016, i.e. 8 years ago.
|
|
34
|
+
* Apart from that, documentation is very sparse.
|
|
33
35
|
* @see {@link https://www.npmjs.com/package/libxmljs|libxmljs}
|
|
34
36
|
*/
|
|
35
37
|
|