feat: add support for markdown extension in readme files#123
Merged
danielroe merged 3 commits intonpmx-dev:mainfrom Jan 26, 2026
Merged
feat: add support for markdown extension in readme files#123danielroe merged 3 commits intonpmx-dev:mainfrom
danielroe merged 3 commits intonpmx-dev:mainfrom
Conversation
|
@idleberg is attempting to deploy a commit to the danielroe Team on Vercel. A member of the Team first needs to authorize it. |
|
Hi! I'm the It looks like you correctly set up a CI job that uses the autofix.ci GitHub Action, but the autofix.ci GitHub App has not been installed for this repository. This means that autofix.ci unfortunately does not have the permissions to fix this pull request. If you are the repository owner, please install the app and then restart the CI workflow! 😃 |
autofix.ci
danielroe
approved these changes
Jan 26, 2026
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
vinnymac
pushed a commit
to vinnymac/npmx.dev
that referenced
this pull request
Jan 28, 2026
sacrosanctic
added a commit
to sacrosanctic/npmx.dev
that referenced
this pull request
Mar 10, 2026
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> ### My notes - enable autodics - need support for dark mode - i18n is causing errors - remove snapshot story (replaced by autodocs) - add a playground story - autodocs has this but requires scrolling #### types of stories - visual stories - only show in autodocs - interactive stories only show in sidebar - test focused stories - only show in sidebar (or not at all? if it isnt visually apparent) ### 🔗 Linked issue <!-- Please ensure there is an open issue and mention its number. For example, "resolves npmx-dev#123" --> ### 🧭 Context <!-- Brief background and why this change is needed --> <!-- High-level summary of what changed --> ### 📚 Description <!-- Describe your changes in detail. Why is this change required? What problem does it solve? --> <!-- If you used AI tools to help with this contribution, please ensure the PR description and code reflect your own understanding. Write in your own voice rather than copying AI-generated text. --> <!---------------------------------------------------------------------- Before creating the pull request, please make sure you do the following: - Check that there isn't already a PR that solves the problem the same way. If you find a duplicate, please help us reviewing it. - Ensure that PR title follows conventional commits (https://www.conventionalcommits.org) - Update the corresponding documentation if needed. - Include relevant tests that fail without this PR but pass with it. - Add any additional context, tradeoffs, follow-ups, or things reviewers should be aware of. Thank you for contributing to npmx! ----------------------------------------------------------------------->
sacrosanctic
added a commit
to sacrosanctic/npmx.dev
that referenced
this pull request
Mar 10, 2026
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> ### My notes - enable autodics - need support for dark mode - i18n is causing errors - remove snapshot story (replaced by autodocs) - add a playground story - autodocs has this but requires scrolling #### types of stories - visual stories - only show in autodocs - interactive stories only show in sidebar - test focused stories - only show in sidebar (or not at all? if it isnt visually apparent) ### 🔗 Linked issue <!-- Please ensure there is an open issue and mention its number. For example, "resolves npmx-dev#123" --> ### 🧭 Context <!-- Brief background and why this change is needed --> <!-- High-level summary of what changed --> ### 📚 Description <!-- Describe your changes in detail. Why is this change required? What problem does it solve? --> <!-- If you used AI tools to help with this contribution, please ensure the PR description and code reflect your own understanding. Write in your own voice rather than copying AI-generated text. --> <!---------------------------------------------------------------------- Before creating the pull request, please make sure you do the following: - Check that there isn't already a PR that solves the problem the same way. If you find a duplicate, please help us reviewing it. - Ensure that PR title follows conventional commits (https://www.conventionalcommits.org) - Update the corresponding documentation if needed. - Include relevant tests that fail without this PR but pass with it. - Add any additional context, tradeoffs, follow-ups, or things reviewers should be aware of. Thank you for contributing to npmx! ----------------------------------------------------------------------->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both GitHub and npm CLI support the
.markdownextension for README files. It's the file-extension endorsed by John Gruber, the inventor of Markdown, but we all know that almost no one uses it. However, since it's a simple change, I thought I'd open a PR. I was unsure regarding the casing; not all file names support all variants. JSDelivr allows them as well, see https://www.jsdelivr.com/package/npm/json-stable-stringify?tab=files&version=1.0.1