Hi Lionel,

Sorry if this is not a right place to ask questions.
I'm building a web app which allows users to create SVG based charts with D3.js and then save them.(These charts will then upload to a server) The problem here is that I cannot convert SVGs to JSONs and send them to the server. I have googled for a few hours and come across your project. It looks like a good fit for my app. But I'm not quite sure if it's capable of:

1. Can be imported with ES6 module syntax or commonJS? I have read through your docs but still not quite understand the browser part.
2. It seems like it only converts SVGs to JSON but not the reverse?

Thank you! Hope you're doing well!

By making the dependency versions more flexible for downstream users you could decrease the possibility that your package becomes a bottleneck for an npm audit fix. I thought of this because I noticed the version we were using of svgson depended on a fixed version of svgo which had a vulnerability. Turns out the only way I can fix it is to do a major upgrade of svgson anyway (it was pre-1.0 svgo), but I noticed you're making lots of commits in the repo just to upgrade dependencies by a patch version increment. You might need to do this less often if you allow flexibility. Downstream users will have their own lockfiles anyway.

Cheers - thanks for sharing the project!

It seems that svgson is adding amp; into my svg image urls where I have ampersands. I'm happy to cater to this but I'm not sure if it is intended or not?

elrumordelaluz/svgson-next#8

Hi! We are just checking to see if the repo is still actively maintained?

thanks!

Before I write something myself, is there an existing library somewhere to query the svgson tree using CSS-like selectors?

Example:

const rects = querySelector('#namedGroup rect')
rects.forEach(rect => {
    rect.attributes.fill = 'red'
})

I am new to this library and I want to know the main the file which contains all the functions such as parse and stringify, actully I wanted import these functions in other javascript file.

Hello, thanks again for another fine project!! I am wondering if you have a JSON schema for the output format of the parse function?

How can we convert the edited JSON back to SVG?

Looking at the code, it seems that everything is synchronous, so I'm wondering why the export returns a promise?

Hey there!

I am currently trying to use svgson to do some bulk operations on some icons.

The source SVG includes <title>Aerom&#233;xico</title>, but when running this through svgson, it returns <title><![CDATA[Aerom&#233;xico]]></title> which causes further issues due to not being a valid HTML tag.

Is there any way to fix this?

I just found out that all default values are removed when the SVG is converted. I.e. if I have a stroke-width="1" im my SVG this is not in the JSON representation of this SVG. That way this can't be further used in a build i.e. for an icon sprite.
Can we introduce an option to keep all attributes, even if they have the default value? That would be awesome :)

Hey,
great library,
I just ran into it today :)

Is it possible to promisify svgson method when working with nodejs?

it will for sure have a good use for it

thanx for sharing 👍 👍 👍

Having problems with the Usage example:

const svgson = require('svgson');

svgson(`
  <svg>
    <line
      stroke= "#bada55"
      stroke-width= "2"
      stroke-linecap= "round"
      x1= "70"
      y1= "80"
      x2= "250"
      y2= "150">
    </line>
  </svg>`).then(json => {
    console.log(JSON.stringify(json, null, 2));
  })

Returns: TypeError: svgson is not a function

Though console logging svgson gives:

{ default: [Function: svgson],
  stringify: [Function: stringify],
  parse: [Function: svgson],
  parseSync: [Function: svgsonSync] }

Calling with svgson.default('<svg>') works.

Environment:
node: 10.16.0
npm: 6.9.0

Currently svgson uses [email protected] by updating to the latest version of 1.0.5 it'd be possible to use convertShapeToPath with circles.

I was trying to merge multiple paths to a single one, when realizing a circle shape is causing problems.

There's an issue with svgo which was fixed in 1.3.2: svg/svgo#1174

Our project currently needs to add "resolutions": { "svgo": "1.3.2" } to package.json when using svgson which is only supported by yarn. Since svgson is our direct requirement, this could be avoided if you made a release with this change and we set that release as a direct minimal requirement.

I'm manipulating text content with svgson, and occasionally the replacement copy includes & symbol.

what happens:
If there is & symbol in the text value the whole block is converted into CDATA

While the escape function for attributes is overridable, the text part is not. The escapeText function prevents the insertion of & or & symbol.

return /[&<>]/.test(str) ? // string escaped into cdata : // string raw pass

I would propose to update the regex so HTML entities like &#\d+; and &\w+; are allowed.

Where does the 5.2.1 version come from? I don't see that tag in github repo?

I want to import the svgson file and use the function parse but without using node js but using statically as ES6 module is it possible, like I tried using the same but I couldn't able to do it as I am getting errors like parse is not defined...
Thanking you.

Use our own function to remove the parent prop, e.g.

export const removeAttrs = (obj) => {
  if (Array.isArray(obj)) {
    for (let i = 0; i < obj.length; i++) {
      obj[i] = removeAttrs(obj[i])
    }
    return obj
  }

  Object.getOwnPropertyNames(obj).forEach((key) => {
    if (key === 'parent') delete obj.parent
    if (obj[key] && typeof obj[key] === 'object') removeAttrs(obj[key])
  })

  return obj
}

The omit-deep package has dependencies itself, namely https://www.npmjs.com/package/unset-value , and that package had some security audit/warnings recently. It has been updated but do we need all the other packages to remove the parent property?

I'm not exactly sure why we need to remove it in first place?

Versions of svgo below 3.0.0 use a deprecated dep that causes a warning: svg/svgo#1689. This is fixed in more recent versions. Are there plans to bump the version this package uses to a more recent one?

For a SVG order of the elements is important. On the other side as per ECMAScript standards, a js object doesn't guarantee the key order. So does this library maintains the order of SVG elements?

Hello,
I figured i should update to the newest svgson, but im not able to get it to work.
I simply used yarn add svgson.

Code:

let json;
try {
  json = await svgson.parse(optimized);
}catch (error) {
  console.log(error);
}

Error:

TypeError: _svgson.default.parse is not a function

My package.json shows "svgson": "^3.0.0"

Any ideas? :)

Hi, just wondering if the --title option in v2 is available in the master branch of the CLI tool? I couldn't seem to get it working