I'm building a static site, which uses ParcelJS to package all the assets. There seems to be an issue with ParcelJS in that it doesn't like that Cloudinary URLs contain commas in the path and this breaks the build as it thinks the Cloudinary URL is pointing to a local resource.
To work around this I encoded the comma in the URL using %2C:
BUT this returns the asset as a PNG, whereas, if I just use commas, then the asset is delivered as an optimized WEBP:
I'm wondering, does your URL parsing handle decoding entities (%2C)? Otherwise, why am I seeing this difference in behaviour?
Please sign in to leave a comment.