InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises. Learn more →
Top 21 JavaScript XML Projects
-
SheetJS js-xlsx
📗 SheetJS Spreadsheet Data Toolkit -- New home https://git.sheetjs.com/SheetJS/sheetjs
xlsx.
-
koodo-reader
A modern ebook manager and reader with sync and backup capacities for Windows, macOS, Linux and Web
My one hope as of now is: https://github.com/troyeguo/koodo-reader
-
Appwrite
Appwrite - The Open Source Firebase alternative introduces iOS support . Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!
-
A bundler running an html transformer like https://github.com/posthtml/posthtml could do this. Then the html would just be dependent on an environment variable to set your prefix conditions.
-
fast-xml-parser
Validate XML, Parse XML and Build XML rapidly without C/C++ based libraries and no callback.
After experimenting with a few different XML parsers I settled on fast-xml-parser. It's fast, it's simple and it's well maintained. It also handles XML namespaces and attributes well. (This appears to be rare in XML parsers.)
-
Project mention: Any well typed NPM packages for converting both ways between XML <-> TS objects... that use a consistent type for XML nodes (with the tag name inside the object)? | reddit.com/r/typescript | 2023-01-24
I found this: https://github.com/nashwaan/xml-js
-
-
camaro
camaro is an utility to transform XML to JSON, using Node.js binding to native XML parser pugixml, one of the fastest XML parser around.
-
InfluxDB
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
-
skyve
Skyve is an open-source low-code platform that gives you access to all of the key capabilities needed to build sophisticated, robust and scalable cloud solutions.
-
xmldom
A pure JavaScript W3C standard-based (XML DOM Level 2 Core) `DOMParser` and `XMLSerializer` module.
-
-
Project mention: [AskJS] Is there any javascript library that can perform boolean operations on svg paths (union, subtract, intersect, difference)? | reddit.com/r/javascript | 2022-07-28
-
-
JokeAPI
REST API that serves uniformly and well formatted jokes in JSON, XML, YAML or plain text format that also offers a great variety of filtering methods
Project mention: Create module for generate random jokes in Telegram bot on NestJS | dev.to | 2022-04-07https://jokeapi.dev/ - site for generate random jokes in English language
-
-
Project mention: Show HN: Xq – command-line XML and HTML beautifier and content extractor | news.ycombinator.com | 2022-11-12
-
I actually made a simple web app a few years ago to do this kind of analytics, and I think maybe your post is responsible for the (mild) activity I am seeing over at the github repo (thanks!). It's nothing too crazy, just a homebrew thing, but you can use it to pull the XML feed from your server and display stats about tags and pull different metrics across libraries (e.g. "How many movies per decade? how many TV shows per network?" etc). I haven't updated it in a long time or maintained it really, so plex may have introduced some breaking changes since I built it. If you're familiar with javascript though it's fairly simple code to edit. You will need to edit some key values either way, such as your private plex token and the ID's of your libraries, but the rest should work out of the box for you (hopefully). I may give it some attention this weekend since people are looking at it again, actually. Either way just wanted to throw it out there.
-
Tableau Connector Pro or another Web Data Connector that can work with JSON. Keisha Rose wrote one that happens to work with Jira. https://github.com/KeshiaRose/JSON-XML-WDC
-
-
super-simple-sitemap-generator
Node powered scraper that iterates trough all the internal links of the specified url. It works on CSR pages (React, Angular) with dynamic urls.
-
Responding to some points I left off here https://news.ycombinator.com/item?id=33336789
I guess the main one is this:
> If your audience is people like me, I think it would probably be worthwhile for you to spend some time up front describing the intended semantics of a data model, as I've attempted above, rather than leaving people to infer it from the grammar. (Maybe OCaml is not a good way to explain it, though.) You might also want to specify that leading and trailing whitespace in prefixes is not significant, though it is in the suffix ("body"); this would enable people to format their name-value pairs readably without corrupting the data. As far as I can tell, this addendum wouldn't interfere with any of your existing uses for Jevko, though in some cases it would simplify their implementations.
You're right, things should be explained more clearly (TODO). Especially the exact role of Jevko and treatment of whitespace. I'll try to improve that.
Here is a sketch of an explanation.
Plain Jevko is meant to be a low-level syntactic layer.
It takes care of turning a unicode sequence into a tree.
On this level, all whitespace is preserved in the tree.
To represent key-value pairs and other data, you most likely want another layer above Jevko -- this would be a Jevko-based format, such as queryjevko (somewhat explained below) or, a very similar one, easyjevko, implemented and very lightly documented here: https://github.com/jevko/easyjevko.js
Or you could have a markup format, such as https://github.com/jevko/markup-experiments#asttoxml5
This format layer defines certain restrictions which may make a subset of Jevkos invalid in it.
It also specifies how to interpret the valid Jevkos. This includes the treatment of whitespace, e.g. that a leading or trailing whitespace in prefixes is insignificant, but conditionally significant in suffixes, etc.
Different formats will define different restrictions and interpretations.
For example:
# queryjevko
queryjevko is a format which uses (a variant of) Jevko as a syntax. Only a subset of Jevko is valid queryjevko.
> I think this is a more useful level of abstraction, and it's more or less the level used by, for example, queryjevko.js's jevkoToJs, although that erroneously uses () instead of [].
The `()` are used on purpose -- queryjevko is meant to be used in URL query strings and be readable. If square brackets were used, things like JS' encodeURIComponent would escape them, making the string unreadable. Using `()` solves that. "~" is used instead of "`" for the same reason. So technically we are dealing not with a spec-compliant Jevko, but a trivial variant of it. Maybe I should write a meta-spec which allows one to pick the three special characters before instantiating itself into a spec. Anyway the parser implementation is configurable in that regard, so I simply configure it to use "~()" instead of "`[]".
> (Also, contrary to your assertion above that this is an example of "leaving [Jevko's data model] as-is", it forgets the order of the name-value pairs as well as I guess all but one of any duplicate set of fields with the same name and also the possibility that there could be both fields and a body.)
I meant [whitespace] rather than [Jevko's data model].
Again, queryjevko is a format which uses Jevko as an underlying syntax. It specifies how syntax trees are converted to JS values, by restricting the range of valid Jevkos. It also specifies conversion in the opposite direction, likewise placing restrictions on JS values that can be safely converted to queryjevko.
The order of name-value pairs happens to get preserved (because of the way JS works), but that's not necessarily relevant. If I were to write a cross-language spec for queryjevko, I'd probably specify that this shouldn't be relied upon.
Duplicate fields and Jevkos with both fields and a non-whitespace body will produce an error when converting Jevko->JS.
I hope this clarifies things somewhat.
Lastly, I'll respond to this for completeness:
> (By the way, if you want to attribute your JSON example for copyright reasons, you need to attribute it to its author or authors, not to the Wikipedia, which is just the site they posted it on.)
According to this:
https://en.wikipedia.org/wiki/Wikipedia:Reusing_Wikipedia_co...
there are 3 options, one of them being what I did, which is to include a link.
I think that's all.
Have a good one!
-
-
Sonar
Write Clean JavaScript Code. Always.. Sonar helps you commit clean code every time. With over 300 unique rules to find JavaScript bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work.
NOTE:
The open source projects on this list are ordered by number of github stars.
The number of mentions indicates repo mentiontions in the last 12 Months or
since we started tracking (Dec 2020).
The latest post mention was on 2023-02-04.
JavaScript XML related posts
- Any Way to Have Film Categories include Count?
- Issue setting up Xteve. Not loading XMLTV url.
- How to set base url for root-relative url?
- Addon for Adult Swim 24/7?
- Create module for generate random jokes in Telegram bot on NestJS
- A step-by-step guide to migrate a Node.js web app to Typescript
- How to find pages on a website with a noindex tag?
-
A note from our sponsor - InfluxDB
www.influxdata.com | 7 Feb 2023
Index
What are some of the best open-source XML projects in JavaScript? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | SheetJS js-xlsx | 32,141 |
| 2 | koodo-reader | 9,140 |
| 3 | posthtml | 2,871 |
| 4 | fast-xml-parser | 1,796 |
| 5 | xml-js | 1,144 |
| 6 | rss-parser | 1,106 |
| 7 | camaro | 479 |
| 8 | skyve | 406 |
| 9 | xmldom | 231 |
| 10 | parse-xml | 222 |
| 11 | svgdom | 210 |
| 12 | TokenScript | 200 |
| 13 | JokeAPI | 168 |
| 14 | sax-wasm | 141 |
| 15 | hred | 56 |
| 16 | medialytics | 31 |
| 17 | JSON-XML-WDC | 23 |
| 18 | DayZLootEditor | 11 |
| 19 | super-simple-sitemap-generator | 9 |
| 20 | markup-experiments | 1 |
| 21 | mdmaker | 0 |
Write Clean JavaScript Code. Always.
Sonar helps you commit clean code every time. With over 300 unique rules to find JavaScript bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work.
www.sonarsource.com