rjgotten
commented
4 years ago the old path for the "module" key in package.json (points inside src instead of dist).
The "module" field is supposed to point to an ES module, which is what ./src contains.
A ./dist folder that's precompiled for browsers should have the "browser" field as its convention.
And a ./dist folder that's meant for Node.js should use the "main" field.
If this actually changed in the repository and its now pointing "module" at ./dist then that's a bug.
Jolg42
The npm package seems to be outdated, since it contains the old path for the "module" key in package.json (points inside src instead of dist).
This leads to importing the non compiled version in eg. the text-to-svg package, so when using it in a web app, the bundle includes arrow functions which breaks the parsing in IE 11.
I would really appreciate if you could publish the current master branch, with that it works flawlessly.
Expected Behavior
The npm package is in sync with the master branch.
Current Behavior
It contains outdated files.
Possible Solution
Publish master to the npm package.
If i use it directly with the git url it works as expected: https://github.com/kboda/text-to-svg/blob/useLocally/package.json#L50