Question 1

HanSON vs JSON5: which one should I use?

Accepted Answer

JSON5 is generally preferred for new projects because it's more actively maintained and widely adopted. HanSON's author recommends JSON5, making it a safer choice with better ecosystem support.

Question 2

How to convert HanSON to JSON in a Node.js project?

Accepted Answer

Install the hanson package via npm with 'npm install -g hanson', then use the command-line tool: 'hanson input.hson output.json'. Alternatively, use the hanson.js library to parse HanSON directly in JavaScript code.

Question 3

Can I use HanSON in browsers without any preprocessing?

Accepted Answer

No, browsers only parse standard JSON, so HanSON files must be converted to JSON first. Use build tools like Webpack with hson-loader or pre-convert files during development.

Question 4

What are the main syntax additions in HanSON compared to JSON?

Accepted Answer

HanSON adds unquoted property names, multi-line strings with backticks, single and double quotes for strings, JavaScript comments, and trailing commas. All valid JSON remains compatible, but HanSON features require conversion for JSON parsers.

Question 5

Is HanSON still maintained or updated?

Accepted Answer

No, the last significant update was in 2016, and the author's note from September 2022 recommends using JSON5 instead, indicating HanSON is effectively deprecated.

Question 6

How do I add multi-line strings in JSON configuration files?

Accepted Answer

With HanSON, use backticks to enclose multi-line strings, as shown in the example with Cookie Monster's background. This avoids escape characters and improves readability.

HanSON

What is HanSON?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions