Prism's use of `global` can introduce bugs in Node
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: Latest
- Plugins: none
- Environment: node
Description
Because Prism uses global, this can cause issues if someone uses multiple modules that use Prism themselves. In my case I have an Eleventy site that uses eleventy-plugin-syntaxhighlight and I'm also building a separate plugin that uses Prism. Because my plugin is required after eleventy-plugin-syntaxhighlight, it causes eleventy-plugin-syntaxhighlight to fail converting some languages.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Node setup with eleventy-plugin-syntaxhighlight and a separate plugin that requires Prism afterward. Trace Prism's use of global and verify that multiple modules can coexist without causing language conversion failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100