Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Doesn’t follow <script href>, <script xlink:href>, <a xlink:href> inside inline <svg>

See original GitHub issue

🐛 bug report

Scripts should be embedded in <svg> with <script href> or <script xlink:href> rather than <script src>, but Parcel doesn’t find scripts with that syntax.

There are also other tags on which it fails to follow xlink:href, like <a>.

🎛 Configuration (.babelrc, package.json, cli command)

$ tail -n +1 *
==> index.html <==
<!DOCTYPE html>
<svg xmlns:xlink="http://www.w3.org/1999/xlink">
  <script xlink:href="script.js"></script>
</svg>

==> script.js <==
alert(1);
$ parcel build index.html
✨  Built in 327ms.

dist/index.html    101 B    266ms

🤔 Expected Behavior

$ ls dist
index.html  script.d1ea37cd.js  script.d1ea37cd.js.map

😯 Current Behavior

$ ls dist
index.html

💁 Possible Solution

Maybe Parcel should follow all href and xlink:href attributes regardless of tag? But if you want a list of applicable tags, MDN has one for href and xlink:href.

🔦 Context

I wanted to embed TypeScript in a standalone SVG file, which didn’t work because Parcel doesn’t scan standalone SVGs for dependencies at all (#3571), but experimentation with inline SVG revealed this additional bug.

💻 Code Sample

See above.

🌍 Your Environment

Software	Version(s)
Parcel	1.12.3
Node	12.10.0
npm/Yarn	1.17.3
Operating System	Ubuntu 19.10

Issue Analytics

State:
Created 4 years ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

anderskcommented, Oct 5, 2019

SVG 2 is a candidate recommendation; SVG 1.1 is still much more common and only supports xlink:href. Do you really think Parcel should require its users to upgrade to candidate technologies? Is there any harm in leaving that decision to the user?

1reaction

DeMoorJaspercommented, Sep 29, 2019

@kirillrogovoy we aren’t really releasing any more updates for v1 so probably best to just fix this for v2