Fix internal links and standardize on npm - #180
Open
ANAMASGARD wants to merge 2 commits into
Open
Conversation
Align documentation iframe fallback links with their embedded iframe sources so non-iframe browsers reach the correct documentation page. Normalize the homepage Get Started link to use a trailing slash, matching the site's configured trailingSlash setting. Signed-off-by: Gaurav Chaudhary <chaudharygaurav2004@gmail.com>
Repository CI uses npm ci. Remove the unused yarn.lock file and update README development instructions to match npm workflows. Signed-off-by: Gaurav Chaudhary <chaudharygaurav2004@gmail.com>
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
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.
Summary
Addresses the existing-link and npm-standardization portions of #156.
Supersedes the stale #157 branch (which would revert news→blog migration and other master changes). This PR contains only 2 commits on current
master:Fix current documentation and navigation links
src(12 files)trailingSlash: trueRemove yarn.lock and standardize on npm
yarn.lock; update README fornpm ci/npm runESLint versus Lychee
The original #157 added a custom ESLint rule. Per @dlebauer review, automated checking is deferred to #135 (Lychee) to avoid overlapping tools. This PR does not include ESLint.
Issue scope
Addresses existing-link fixes and npm standardization from #156. Automated link checking remains deferred to #135.
Does not claim to close #156 unless maintainers agree to narrow scope.
Verification
npm ci— exit 0, no lockfile changesnpm run build— exit 0/,/documentation/latest/,/blog/,/news/— OKSigned-off-by: ANAMASGARD