Add query parameter for pane widths

[jamilahmadzai]

Fixes #63.

This adds a widths query parameter for embedded CodePan layouts, so iframe users can choose pane proportions alongside the existing show parameter.

What changed:

• supports positional widths that match the visible pane order, for example widths=25,25,50
• supports named widths for order-independent embeds, for example widths=js:25,console:25,output:50
• normalizes relative values like 1,1,2 and accepts optional % suffixes
• falls back to the existing equal-width layout when widths is missing, invalid, or does not cover every visible pane
• updates the embed docs and adds focused parser/position tests

Validation:

• corepack yarn run test:pan-widths
• npx -y -p node@18 -c 'corepack yarn test'
• git diff --check

Bounty:

• IssueHunt bounty-platform payout to GitHub user @jamilahmadzai if accepted.

---

IssueHunt Summary

Referenced issues

This pull request has been submitted to:

• #63: add query string parameters for setting panel width

---

[vercel]

@jamilahmadzai is attempting to deploy a commit to the EGOIST's projects Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: Exposure of Sensitive Information in npm eventsource CVE: GHSA-6h5x-7c5m-7cr7 Exposure of Sensitive Information in eventsource (CRITICAL) Affected versions: < 1.1.1; >= 2.0.0 < 2.0.2 Patched version: 1.1.1 From: ? → npm/poi@9.6.7 → npm/eventsource@0.1.6 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/eventsource@0.1.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: npm thenify before 3.3.1 made use of unsafe calls to `eval`. CVE: GHSA-29xr-v42j-r956 thenify before 3.3.1 made use of unsafe calls to eval. (CRITICAL) Affected versions: < 3.3.1 Patched version: 3.3.1 From: ? → npm/poi@9.6.7 → npm/thenify@3.3.0 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/thenify@3.3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm node-forge is 95.0% likely obfuscated Confidence: 0.95 Location: Package overview From: ? → npm/poi@9.6.7 → npm/node-forge@0.6.33 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-forge@0.6.33. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report