Skip to content
This repository was archived by the owner on Apr 3, 2024. It is now read-only.

Comments

fix: Relative GitHub paths when a directory is specified#455

Open
mofojed wants to merge 1 commit intonpm:masterfrom
mofojed:fix-relative-directory
Open

fix: Relative GitHub paths when a directory is specified#455
mofojed wants to merge 1 commit intonpm:masterfrom
mofojed:fix-relative-directory

Conversation

@mofojed
Copy link

@mofojed mofojed commented Mar 1, 2022

- Check for the `directory` property on the repository, for when package.json is not at the root: https://docs.npmjs.com/cli/v7/configuring-npm/package-json#repository
- Convert the relative path correctly to where the file is located in GitHub
mofojed added a commit to mofojed/web-client-ui that referenced this pull request Mar 7, 2022
npmjs doesn't handle the `directory` spec in package.json when building links. I've made a separate PR to fix that, but I doubt it will ever be merged: npm/marky-markdown#455

Workaround is to just use absolute links.
dsmmcken pushed a commit to deephaven/web-client-ui that referenced this pull request Mar 11, 2022
npmjs doesn't handle the `directory` spec in package.json when building links. I've made a separate PR to fix that, but I doubt it will ever be merged: npm/marky-markdown#455

Workaround is to just use absolute links.
@mofojed mofojed changed the title Fix relative GitHub paths when a directory is specified fix: Relative GitHub paths when a directory is specified Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant