@salesforcedevs/sfdocs-no-relative-link-in-shared-md
Advanced tools
Validate the relative links in shared folder and throw error/warning after check
We shouldn't allow relative links for cross references in markdown files for shared folder.
Always use absolute links for any specific markdown in Shared folder files. So all absolute links should start with /docs or we can use any external links.
This linter takes up folder name as input. If there are any relative links within the specified folder it will throw error while validating as it doesn't have toc.yml entry.
This validation is added to make the yarn start and yarn validate consistent as the above scenario will create a broken link.
yarn install && yarn build
yarn publish
Please make sure to push your changes (version number & other changes) to git once publishing is complete.
FAQs
Validate the relative links in shared folder and throw error/warning after check
The npm package @salesforcedevs/sfdocs-no-relative-link-in-shared-md receives a total of 0 weekly downloads. As such, @salesforcedevs/sfdocs-no-relative-link-in-shared-md popularity was classified as not popular.
We found that @salesforcedevs/sfdocs-no-relative-link-in-shared-md demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.