PrismJS / PrismJS/prism

Prism Autoloader 1.28.0 and 1.29.0 fetches unavailable JS files from Cloudflare CDN

Open
#3,595 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13k
Forks
1.4k
Avg merge
15h 36m
Merged PRs (30d)
3

Description

Information:

  • Prism version: 1.28.0 and 1.29.0
  • Plugins: none
  • Environment: Browser

Description
Prism autoloader 1.28.0 and 1.29.0 tries to fetch JavaScript resources from Cloudflare CDN that are not available. This leads to a few 404 Not Found responses.

Autoloader was embedded as follows:

<script src="https://cdnjs.cloudflare.com/ajax/libs/prism/1.28.0/plugins/autoloader/prism-autoloader.min.js" integrity="sha512-fTl/qcO1VgvKtOMApX2PdZzkziyr2stM65GYPLGuYMnuMm1z2JLJG6XVU7C/mR+E7xBUqCivykuhlzfqxXBXbg==" crossorigin="anonymous" referrerpolicy="no-referrer"></script>

The following scripts are tried to be fetched that do not resolve properly:

image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Prism autoloader script at plugins/autoloader/prism-autoloader.min.js and trace how it constructs component URLs. Check the component references for prism-conf.min.js and prism-iql.min.js against the listed Cloudflare CDN paths; done means the autoloader no longer requests unavailable resources and the affected URLs resolve correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.