chore(deps): bump rspress to v2.0.0-beta.22 #143
Conversation
JounQin
added
bug
🦋 Changeset detectedLatest commit: c6bf6e8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Warning Rate limit exceeded@JounQin has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 44 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (65)
WalkthroughThis update migrates all imports and dependencies from the unscoped Changes
Sequence Diagram(s)sequenceDiagram
participant App
participant @rspress/core
participant @rspress/core/runtime
participant @rspress/core/theme
App->>@rspress/core: Import core functions/types (logger, serve, build, dev, RspressPlugin, UserConfig)
App->>@rspress/core/runtime: Import runtime hooks (useI18n, useLang, usePageData, isProduction, withBase, useDark)
App->>@rspress/core/theme: Import/re-export theme components (Badge, Card, Tab, Tabs, Steps, Toc, LinkCard, SourceCode, etc.)
Note over App: All previous imports from unscoped 'rspress' are now from '@rspress/core' packages
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Poem
✨ Finishing Touches
🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Pull Request Overview
This PR upgrades RSPress to version 2.0.0-beta.22, which includes significant changes to the import paths structure. The upgrade moves from direct rspress/* imports to scoped @rspress/* imports, aligning with the new package organization.
- Updates all import statements from
rspress/*to@rspress/core/*and related scoped packages - Upgrades package dependencies including RSPress core, plugins, and related tools
- Updates documentation examples to reflect the new import paths
Reviewed Changes
Copilot reviewed 56 out of 57 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| package.json | Updates RSPress dependencies to v2.0.0-beta.22 and adds @rspress/core package |
| src/utils/git.ts | Updates logger import from rspress/core to @rspress/core |
| src/types.ts | Updates serve import from rspress/core to @rspress/core |
| src/theme.tsx | Updates all runtime and theme imports to use @rspress/core paths |
| src/shared/helpers.ts | Reorganizes imports from @rspress/shared and @rspress/core |
| src/runtime/hooks/* | Updates runtime hook imports to @rspress/core/runtime |
| src/runtime/components/* | Updates all component imports to @rspress/core/theme and @rspress/core/runtime |
| src/plugins/* | Updates all plugin type imports to @rspress/core |
| src/global/* | Updates runtime and theme imports to @rspress/core paths |
| src/cli/* | Updates core functionality imports to @rspress/core |
| docs/* | Updates documentation examples with new import paths |
commit: |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🔭 Outside diff range comments (2)
src/types.ts (1)
2-15:typeof servebreaks with a type-only import – droptypeof.
serveis imported withimport type, therefore it is only a type alias.
Usingtypeof serverequires a value-level symbol and will trigger:"serve" cannot be used as a value because it was imported using 'import type'.Replace
Parameters<typeof serve>[0]withParameters<serve>[0], or importserveas a regular (non-type) import if you really needtypeof.-export type BaseServeOptions = Parameters<typeof serve>[0] +export type BaseServeOptions = Parameters<serve>[0]src/shared/helpers.ts (1)
48-55: Regex injection / false-positive risk when matching active nav item
new RegExp(item.activeMatch || item.link)interprets any meta-characters contained inlink(?,.…) as regex tokens, which can:
- Break on unescaped chars (
[,(…) → runtime error.- Mark unrelated paths active.
Escaping the pattern (or expecting
activeMatchto be a pre-validated regex) avoids both issues:-import type { escapeRegExp } from 'lodash-es' // if lodash already in deps -… - new RegExp(item.activeMatch || item.link).test( + const pattern = item.activeMatch || escapeRegExp(item.link) + new RegExp(pattern).test((or roll your own tiny
escapeRegExpto avoid the dependency).
🧹 Nitpick comments (3)
src/runtime/components/Mermaid.tsx (1)
21-23: Optional: avoid repeated global initialisation
mermaid.initializemutates global config and is re-invoked every timeisDarkchanges. Consider calling it once (or usingmermaidAPI.updateSiteConfig) to reduce overhead.src/shared/helpers.ts (1)
23-30: Explicit return type would help downstream callers
getUnversionedVersioncurrently returnsstring | undefined, but the lack of an explicit annotation forces consumers (and the compiler) to infer. A quick annotation keeps the public surface crystal-clear:-export const getUnversionedVersion = (version?: string) => { +export const getUnversionedVersion = (version?: string): string | undefined => {src/runtime/components/Overview.tsx (1)
12-12: Mixed source packages (@rspress/runtime+@rspress/core)
Nothing wrong here, just flagging that runtime utilities remain in@rspress/runtimewhile theme/types came from@rspress/core. If the upstream ever consolidates again, this import split is the first place to update.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
yarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (57)
.changeset/quick-dryers-burn.md(1 hunks)docs/en/usage/mdx.mdx(1 hunks)docs/zh/usage/mdx.mdx(1 hunks)fixture-docs/en/index.mdx(1 hunks)fixture-docs/ru/index.mdx(1 hunks)fixture-docs/zh/index.mdx(1 hunks)package.json(4 hunks)src/cli/export.ts(1 hunks)src/cli/index.ts(1 hunks)src/cli/lint.ts(1 hunks)src/cli/load-config.ts(1 hunks)src/cli/translate.ts(1 hunks)src/global/SiteOverrides/index.tsx(1 hunks)src/global/VersionsNav/NavMenuGroup.tsx(1 hunks)src/global/VersionsNav/NavMenuSingleItem.tsx(1 hunks)src/global/VersionsNav/index.tsx(1 hunks)src/plugins/api/index.ts(1 hunks)src/plugins/attributes/index.ts(1 hunks)src/plugins/auto-sidebar/index.ts(1 hunks)src/plugins/auto-sidebar/utils.ts(1 hunks)src/plugins/auto-sidebar/walk.ts(1 hunks)src/plugins/auto-toc/index.ts(1 hunks)src/plugins/directives/index.ts(1 hunks)src/plugins/global/index.ts(1 hunks)src/plugins/mermaid/index.ts(1 hunks)src/plugins/permission/index.ts(1 hunks)src/plugins/replace/index.ts(1 hunks)src/plugins/replace/remark-replace.ts(1 hunks)src/plugins/replace/resolve-reference.ts(1 hunks)src/plugins/replace/resolve-release.ts(1 hunks)src/plugins/replace/utils.ts(1 hunks)src/plugins/sitemap/index.ts(1 hunks)src/runtime/components/Badge.ts(1 hunks)src/runtime/components/Card.ts(1 hunks)src/runtime/components/ExternalSiteLink.tsx(1 hunks)src/runtime/components/JsonViewer.tsx(1 hunks)src/runtime/components/K8sCrd.tsx(1 hunks)src/runtime/components/K8sPermissionTable.tsx(1 hunks)src/runtime/components/LinkCard.ts(1 hunks)src/runtime/components/Mermaid.tsx(1 hunks)src/runtime/components/OpenAPIPath.tsx(1 hunks)src/runtime/components/OpenAPIRef.tsx(1 hunks)src/runtime/components/Overview.tsx(1 hunks)src/runtime/components/PackageManagerTabs.ts(1 hunks)src/runtime/components/Steps.ts(1 hunks)src/runtime/components/Tab.ts(1 hunks)src/runtime/components/Tabs.tsx(1 hunks)src/runtime/components/Toc.ts(1 hunks)src/runtime/components/_ExternalSiteBase.tsx(1 hunks)src/runtime/components/_X.tsx(1 hunks)src/runtime/components/_utils.ts(1 hunks)src/runtime/hooks/useSiteOverrides.ts(1 hunks)src/runtime/hooks/useTranslation.ts(1 hunks)src/shared/helpers.ts(1 hunks)src/theme.tsx(2 hunks)src/types.ts(1 hunks)src/utils/git.ts(1 hunks)
🧰 Additional context used
🧠 Learnings (58)
📓 Common learnings
Learnt from: JounQin
PR: alauda/doom#30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: alauda/doom#30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like `@rspress/core/theme` work without any ESLint errors.
Learnt from: JounQin
PR: alauda/doom#30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as `"./theme": { "default": "./theme.ts" }`, so imports like `import { Badge, Button } from '@rspress/core/theme'` are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: alauda/doom#40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like `import { logger } from '@rspress/shared/logger'` are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: alauda/doom#34
File: src/cli/load-config.ts:290-0
Timestamp: 2025-05-29T10:23:34.965Z
Learning: In the @alauda/doom project, JounQin prefers concise error handling over verbose validation. While they prefer throwing on invalid configuration rather than graceful fallbacks, they don't want overly detailed validation with multiple explicit checks and error messages.
src/plugins/api/index.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
docs/en/usage/mdx.mdx (4)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
src/plugins/auto-sidebar/utils.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
.changeset/quick-dryers-burn.md (4)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #75
File: src/cli/load-config.ts:4-7
Timestamp: 2025-06-09T03:10:41.010Z
Learning: The alauda/doom project uses yarn v4 as the package manager, not npm. Always reference yarn commands when suggesting package management operations.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
src/runtime/components/PackageManagerTabs.ts (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
fixture-docs/ru/index.mdx (5)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #117
File: src/remark-lint/no-heading-punctuation.ts:4-4
Timestamp: 2025-07-09T02:33:05.638Z
Learning: In the @alauda/doom project, JounQin prefers to keep the toString import from mdast-util-to-string as is, even though it shadows the global toString property. Variable shadowing warnings for this specific case should not be flagged as issues.
src/runtime/components/OpenAPIRef.tsx (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/types.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/utils/git.ts (5)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #9
File: src/cli/load-config.ts:27-27
Timestamp: 2025-05-12T11:11:41.048Z
Learning: The yoctocolors package is used in the codebase for colored terminal output, with the cyan function imported in src/cli/load-config.ts.
fixture-docs/en/index.mdx (5)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #117
File: src/remark-lint/no-heading-punctuation.ts:4-4
Timestamp: 2025-07-09T02:33:05.638Z
Learning: In the @alauda/doom project, JounQin prefers to keep the toString import from mdast-util-to-string as is, even though it shadows the global toString property. Variable shadowing warnings for this specific case should not be flagged as issues.
src/plugins/mermaid/index.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/plugins/replace/resolve-reference.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/plugins/replace/utils.ts (5)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #9
File: src/cli/load-config.ts:27-27
Timestamp: 2025-05-12T11:11:41.048Z
Learning: The yoctocolors package is used in the codebase for colored terminal output, with the cyan function imported in src/cli/load-config.ts.
src/runtime/components/K8sCrd.tsx (1)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
src/plugins/permission/index.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/runtime/components/ExternalSiteLink.tsx (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/runtime/hooks/useSiteOverrides.ts (6)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #34
File: src/theme.tsx:4-17
Timestamp: 2025-05-29T10:21:32.682Z
Learning: In the @alauda/doom project, environment variables like ALGOLIA_APP_ID, ALGOLIA_API_KEY, and ALGOLIA_INDEX_NAME are injected at build time, making non-null assertions safe when used after truthiness checks.
Learnt from: JounQin
PR: #117
File: src/remark-lint/no-heading-punctuation.ts:4-4
Timestamp: 2025-07-09T02:33:05.638Z
Learning: In the @alauda/doom project, JounQin prefers to keep the toString import from mdast-util-to-string as is, even though it shadows the global toString property. Variable shadowing warnings for this specific case should not be flagged as issues.
src/plugins/auto-toc/index.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/runtime/components/Tabs.tsx (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
src/runtime/components/LinkCard.ts (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/runtime/components/Badge.ts (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/plugins/replace/index.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
docs/zh/usage/mdx.mdx (4)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
src/plugins/replace/resolve-release.ts (5)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #9
File: src/cli/load-config.ts:27-27
Timestamp: 2025-05-12T11:11:41.048Z
Learning: The yoctocolors package is used in the codebase for colored terminal output, with the cyan function imported in src/cli/load-config.ts.
src/runtime/components/_ExternalSiteBase.tsx (6)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #117
File: src/remark-lint/no-heading-punctuation.ts:4-4
Timestamp: 2025-07-09T02:33:05.638Z
Learning: In the @alauda/doom project, JounQin prefers to keep the toString import from mdast-util-to-string as is, even though it shadows the global toString property. Variable shadowing warnings for this specific case should not be flagged as issues.
Learnt from: JounQin
PR: #117
File: src/remark-lint/constants.ts:1-1
Timestamp: 2025-07-09T02:31:06.588Z
Learning: In the @alauda/doom project, PUNCTUATION_REGEX in src/remark-lint/constants.ts is only used for test() operations, so the global flag is not needed and the current implementation /\p{P}/u is correct.
src/plugins/global/index.ts (5)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #117
File: src/remark-lint/constants.ts:1-1
Timestamp: 2025-07-09T02:31:06.588Z
Learning: In the @alauda/doom project, PUNCTUATION_REGEX in src/remark-lint/constants.ts is only used for test() operations, so the global flag is not needed and the current implementation /\p{P}/u is correct.
src/runtime/components/JsonViewer.tsx (4)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
fixture-docs/zh/index.mdx (5)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #117
File: src/remark-lint/no-heading-punctuation.ts:4-4
Timestamp: 2025-07-09T02:33:05.638Z
Learning: In the @alauda/doom project, JounQin prefers to keep the toString import from mdast-util-to-string as is, even though it shadows the global toString property. Variable shadowing warnings for this specific case should not be flagged as issues.
src/plugins/attributes/index.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/global/SiteOverrides/index.tsx (3)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/plugins/directives/index.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/global/VersionsNav/index.tsx (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/plugins/replace/remark-replace.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/runtime/components/K8sPermissionTable.tsx (3)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/runtime/components/_X.tsx (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
src/cli/lint.ts (5)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #75
File: src/cli/load-config.ts:4-7
Timestamp: 2025-06-09T03:10:41.010Z
Learning: The alauda/doom project uses yarn v4 as the package manager, not npm. Always reference yarn commands when suggesting package management operations.
src/cli/load-config.ts (6)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #9
File: src/cli/load-config.ts:27-27
Timestamp: 2025-05-12T11:11:41.048Z
Learning: The yoctocolors package is used in the codebase for colored terminal output, with the cyan function imported in src/cli/load-config.ts.
Learnt from: JounQin
PR: #117
File: src/remark-lint/no-heading-punctuation.ts:4-4
Timestamp: 2025-07-09T02:33:05.638Z
Learning: In the @alauda/doom project, JounQin prefers to keep the toString import from mdast-util-to-string as is, even though it shadows the global toString property. Variable shadowing warnings for this specific case should not be flagged as issues.
src/runtime/components/_utils.ts (2)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
src/cli/translate.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/runtime/components/OpenAPIPath.tsx (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/shared/helpers.ts (3)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/runtime/components/Tab.ts (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/cli/index.ts (6)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #69
File: package.json:101-101
Timestamp: 2025-06-06T07:08:55.881Z
Learning: When a package has peer dependencies that require TypeScript (like @eslint-react/eslint-plugin), TypeScript should be moved from devDependencies to dependencies to satisfy the peer dependency requirement.
Learnt from: JounQin
PR: #69
File: package.json:101-101
Timestamp: 2025-06-06T07:08:55.881Z
Learning: When a package has peer dependencies that require TypeScript (like @eslint-react/eslint-plugin), TypeScript should be moved from devDependencies to dependencies to satisfy the peer dependency requirement.
src/global/VersionsNav/NavMenuGroup.tsx (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/plugins/sitemap/index.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/runtime/hooks/useTranslation.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/runtime/components/Card.ts (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
package.json (8)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #69
File: package.json:101-101
Timestamp: 2025-06-06T07:08:55.881Z
Learning: When a package has peer dependencies that require TypeScript (like @eslint-react/eslint-plugin), TypeScript should be moved from devDependencies to dependencies to satisfy the peer dependency requirement.
Learnt from: JounQin
PR: #69
File: package.json:101-101
Timestamp: 2025-06-06T07:08:55.881Z
Learning: When a package has peer dependencies that require TypeScript (like @eslint-react/eslint-plugin), TypeScript should be moved from devDependencies to dependencies to satisfy the peer dependency requirement.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #75
File: src/cli/load-config.ts:4-7
Timestamp: 2025-06-09T03:09:17.876Z
Learning: When ESLint shows "Unable to resolve path to module" errors for packages that are listed in package.json dependencies, the issue is usually that npm install hasn't been run yet, not that the packages are missing from dependencies or that there's an ESLint configuration problem.
Learnt from: JounQin
PR: #75
File: src/cli/load-config.ts:4-7
Timestamp: 2025-06-09T03:10:41.010Z
Learning: The alauda/doom project uses yarn v4 as the package manager, not npm. Always reference yarn commands when suggesting package management operations.
src/runtime/components/Mermaid.tsx (4)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/cli/export.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/runtime/components/Toc.ts (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/plugins/auto-sidebar/walk.ts (3)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/runtime/components/Steps.ts (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/plugins/auto-sidebar/index.ts (4)
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
src/global/VersionsNav/NavMenuSingleItem.tsx (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/runtime/components/Overview.tsx (3)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
src/theme.tsx (4)
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T08:59:41.491Z
Learning: In @rspress/core v2.0.0-beta.7, the '/theme' export is available in the package exports field as "./theme": { "default": "./theme.ts" }, so imports like import { Badge, Button } from '@rspress/core/theme' are valid even if ESLint shows resolution errors.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: The alauda/doom project uses yarn v4 for dependency management, which handles package exports and module resolution correctly, so imports like @rspress/core/theme work without any ESLint errors.
Learnt from: JounQin
PR: #40
File: src/plugins/sitemap/index.ts:7-7
Timestamp: 2025-05-29T16:25:28.086Z
Learning: In @rspress/shared v2.0.0-beta.8, the '/logger' export is available in the package exports field, so imports like import { logger } from '@rspress/shared/logger' are valid even if ESLint shows resolution errors. This is used throughout the codebase in files like src/cli/translate.ts, src/cli/load-config.ts, src/utils/git.ts, and src/plugins/sitemap/index.ts.
Learnt from: JounQin
PR: #30
File: src/runtime/components/K8sCrd.tsx:5-5
Timestamp: 2025-05-26T09:09:21.339Z
Learning: JounQin has mentioned multiple times that the alauda/doom project uses yarn v4, and there are no ESLint import resolution errors for @rspress/core subpath imports.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
- GitHub Check: Build and Lint with Node.js 24 on ubuntu-latest
- GitHub Check: Build and Lint with Node.js 20 on ubuntu-latest
- GitHub Check: Build and Lint with Node.js 22 on ubuntu-latest
- GitHub Check: Build and Lint with Node.js 18 on ubuntu-latest
- GitHub Check: Build and Lint with Node.js 22 on ubuntu-latest
- GitHub Check: Build and Lint with Node.js 20 on ubuntu-latest
- GitHub Check: Build and Lint with Node.js 18 on ubuntu-latest
🔇 Additional comments (61)
fixture-docs/ru/index.mdx (1)
5-5: Import path correctly migrated to the scoped package
@rspress/core/runtimeis the new canonical entry-point in v2.x; the update keeps the fixture in sync with the dependency bump.
No further action required.fixture-docs/zh/index.mdx (1)
5-5: Consistent namespace updateThe runtime import now points to
@rspress/core/runtime, matching the remainder of the migration work. Looks good.fixture-docs/en/index.mdx (1)
1-1: Scoped runtime import looks goodImport path aligns with the bumped
@rspress/corepackage; no issues spotted..changeset/quick-dryers-burn.md (1)
1-6: Changeset captures the dependency bump correctlyThe new patch-level changeset documents the upgrade and will ensure versioning flows through on release.
src/plugins/auto-toc/index.ts (1)
1-1: Plugin type import updated to scoped core – looks correct
RspressPluginnow resolves from@rspress/core, matching the new package name. Build/type-check should continue to pass.src/runtime/components/Tabs.tsx (1)
1-1: Import path correctly moved to scoped package
Switching to@rspress/core/themematches the dependency bump and preserves type re-exports. No further action needed.src/runtime/hooks/useSiteOverrides.ts (1)
1-1: Runtime helpers import updated as expected
isProductionandwithBasenow resolve from@rspress/core/runtime; this is the correct location after the package split. Looks good.src/utils/git.ts (1)
5-5: Logger import migrated successfully
Importingloggerfrom@rspress/corealigns with the new namespace; no behavioural impact on the git helper.src/plugins/permission/index.ts (1)
1-1: Plugin type import updated
TheRspressPlugintype now comes from@rspress/core; this keeps typings intact with the bumped version.src/plugins/mermaid/index.ts (1)
1-1: Scoped core import looks correct
Import path change is consistent with the rest of the migration; no issues detected.src/plugins/attributes/index.ts (1)
1-1: Import path update looks correct.
RspressPluginnow comes from the scoped package – consistent with the dependency bump. No other concerns.src/runtime/components/JsonViewer.tsx (1)
1-1: Scoped theme import LGTM.The switch to
@rspress/core/themeis aligned with the package re-scoping; no further action required.src/plugins/replace/utils.ts (1)
1-1: Action Needed: Confirmloggerexport sourceIt looks like
@rspress/coredoes not re-exportlogger(no./loggerin its package exports or root files), which will cause a runtime error.Please verify and adjust accordingly:
- File:
src/plugins/replace/utils.ts- Current import:
import { logger } from '@rspress/core'- Suggested options:
- Revert to the original import:
import { logger } from '@rspress/shared/logger'- Or add a
loggerre-export in@rspress/coreupstreamsrc/runtime/components/K8sCrd.tsx (1)
5-5: Theme import path update acknowledged.The new scoped path matches the rest of the migration and keeps the component tree intact.
src/plugins/directives/index.ts (1)
1-1: Scoped import looks correctSwitching to
@rspress/corematches the dependency bump and compiles fine with Yarn v4’s export resolution. No further action required.src/plugins/replace/resolve-release.ts (1)
1-1: Confirmedloggerre-export in @rspress/core
Theloggersymbol is exposed indist/index.jsof @rspress/core@2.0.0-beta.22 (line 2640), so importingloggerfrom@rspress/corewill work as expected. No action required.src/runtime/components/_ExternalSiteBase.tsx (1)
1-1: Import path updated correctly
useLangnow comes from@rspress/core/runtime; this aligns with the scoped-package migration and should compile cleanly.src/runtime/components/Mermaid.tsx (1)
1-1: Import path migration acknowledgedHook source switched to the scoped runtime module; looks good.
src/plugins/api/index.ts (2)
2-2: Scoped type import LGTM
RspressPluginis now pulled from@rspress/core; matches the new dependency scope.
1-2: No stale unscopedrspress/...imports detectedI scanned the entire codebase for any
import ... from 'rspress/...occurrences using bothrgandgrepand found no matches. No further action is needed.src/runtime/components/OpenAPIRef.tsx (1)
1-1: Scoped import looks correct
Import path migrated to the new@rspress/core/runtimenamespace and matches the project-wide move. No additional changes required here.src/runtime/components/K8sPermissionTable.tsx (1)
1-1: Import path updated successfully
The switch to@rspress/core/runtimealigns with the dependency bump; no other impacts detected.src/global/SiteOverrides/index.tsx (1)
1-1: LGTM – migration complete
Scoped runtime import is correct and consistent with the rest of the refactor.src/plugins/replace/index.ts (1)
3-4: Core & logger imports migrated
Both type and value imports now point at@rspress/core, which matches the new package structure. Build tooling should resolve this without additional config under Yarn v4.src/runtime/components/ExternalSiteLink.tsx (1)
1-1: Runtime hook import migrated correctly
The consolidated import from@rspress/core/runtimelooks good and keeps tree-shaking intact.docs/en/usage/mdx.mdx (1)
26-26: Documentation example updated correctly.The import path change from
'rspress/theme'to'@rspress/core/theme'properly reflects the new scoped package structure. This ensures users following the documentation will use the correct import syntax.docs/zh/usage/mdx.mdx (1)
25-25: Documentation example updated correctly.The import path change from
'rspress/theme'to'@rspress/core/theme'properly reflects the new scoped package structure, maintaining consistency with the English documentation.src/runtime/components/_X.tsx (1)
1-1: Import path updated correctly.The migration from
'rspress/theme'to'@rspress/core/theme'for thegetCustomMDXComponentimport aligns with the dependency upgrade to the scoped package structure.src/cli/translate.ts (1)
7-7: Logger import updated correctly.The migration from
'rspress/core'to'@rspress/core'for the logger import aligns with the dependency upgrade to the scoped package structure.src/plugins/auto-sidebar/utils.ts (1)
4-4: Logger import updated correctly.The migration from
'rspress/core'to'@rspress/core'for the logger import aligns with the dependency upgrade to the scoped package structure.src/cli/lint.ts (1)
3-3: LGTM: Import path successfully migrated to scoped package.The import has been correctly updated from the unscoped
rspress/coreto the scoped@rspress/corepackage as part of the systematic migration to v2.0.0-beta.22.src/cli/index.ts (1)
11-11: LGTM: Import path successfully migrated to scoped package.The import has been correctly updated from the unscoped
rspress/coreto the scoped@rspress/corepackage, maintaining the same exported functions while using the new package structure.src/runtime/components/OpenAPIPath.tsx (1)
1-2: LGTM: Import paths successfully migrated to scoped packages.Both imports have been correctly updated:
usePageDatafromrspress/runtimeto@rspress/core/runtimeBadgefromrspress/themeto@rspress/core/themeThe subpath exports are properly supported in the new package structure.
src/plugins/replace/resolve-reference.ts (1)
4-4: LGTM: Import path successfully migrated to scoped package.The logger import has been correctly updated from the unscoped
rspress/coreto the scoped@rspress/corepackage as part of the systematic migration.src/cli/export.ts (1)
4-4: LGTM: Import path successfully migrated to scoped package.The import has been correctly updated from the unscoped
rspress/coreto the scoped@rspress/corepackage, maintaining bothloggerandserveimports while using the new package structure.src/runtime/hooks/useTranslation.ts (1)
1-1: LGTM: Clean import migration to scoped package.The import path update from
'rspress/runtime'to'@rspress/core/runtime'is consistent with the broader package migration and maintains the same functionality.src/plugins/replace/remark-replace.ts (1)
6-6: LGTM: Consistent logger import migration.The import path update from
'rspress/core'to'@rspress/core'aligns with the broader package migration and maintains the same logger functionality.src/global/VersionsNav/NavMenuGroup.tsx (1)
1-2: LGTM: Import consolidation under @rspress/core namespace.The import updates consolidate
NavItemWithLinkandTagimports under the@rspress/coreand@rspress/core/themepackages respectively, which aligns with the package migration strategy.src/runtime/components/_utils.ts (1)
5-6: LGTM: Logical import reorganization between core and shared packages.The reorganization separates sidebar component types (
@rspress/core) from shared types (@rspress/shared), which provides better separation of concerns while maintaining functionality.src/plugins/sitemap/index.ts (1)
6-6: LGTM: Clean import consolidation.Consolidating both
loggerandRspressPluginimports from@rspress/coresimplifies the import structure and aligns with the package migration strategy.src/runtime/components/PackageManagerTabs.ts (1)
4-4: LGTM! Clean migration to scoped package.The update from
'rspress/theme'to'@rspress/core/theme'aligns with the systematic package migration across the codebase.src/global/VersionsNav/index.tsx (1)
1-6: LGTM! Consistent migration to scoped runtime package.The import path update from
'rspress/runtime'to'@rspress/core/runtime'follows the established migration pattern and maintains all existing functionality.src/runtime/components/Tab.ts (1)
1-1: LGTM! Consistent theme component migration.The export path update to
'@rspress/core/theme'follows the established pattern for theme component migrations.src/runtime/components/LinkCard.ts (1)
1-1: LGTM! Theme component migration completed correctly.The LinkCard export path update maintains consistency with the broader scoped package migration.
src/runtime/components/Badge.ts (1)
1-1: LGTM! Badge component migration follows established pattern.The export path update to
'@rspress/core/theme'completes the systematic migration for this set of theme components.src/shared/helpers.ts (1)
1-2: Import split looks goodType vs value separation is correct and aligns with the new
@rspress/*package layout. No further action required.src/global/VersionsNav/NavMenuSingleItem.tsx (1)
1-3: Import path updates are correctThe switch to scoped packages (
@rspress/*) is accurate; nothing else to flag here.src/plugins/global/index.ts (1)
4-5: Good migrationType/value split and new import paths look correct. No functional impact.
src/runtime/components/Card.ts (1)
1-1: Re-export path updated successfullyExport now matches the new theme location. ✅
src/runtime/components/Toc.ts (1)
1-1: Re-export path updated successfullyConsistent with the rest of the theme components.
src/runtime/components/Steps.ts (1)
1-1: LGTM! Import path correctly updated to scoped package.The migration from
'rspress/theme'to'@rspress/core/theme'is consistent with the dependency upgrade and aligns with the scoped package restructuring.src/plugins/auto-sidebar/index.ts (1)
3-4: LGTM! Import reorganization follows logical package structure.Moving
RspressPluginandUserConfigtypes to@rspress/corewhile keeping theaddTrailingSlashutility in@rspress/sharedcreates a clear separation between core types and shared utilities.src/plugins/auto-sidebar/walk.ts (1)
4-18: LGTM! Import reorganization properly categorizes utilities.The redistribution of imports between
@rspress/coreand@rspress/sharedcreates logical separation:
- Core runtime utilities (
logger,withBase) moved to@rspress/core- General utility functions (
isExternalUrl,removeLeadingSlash,slash) and shared types (NavItem) moved to@rspress/sharedsrc/cli/load-config.ts (1)
9-9: LGTM! Import consolidation simplifies dependency structure.Consolidating both
loggerandUserConfigimports from@rspress/corereduces import complexity and properly groups core functionality together.src/theme.tsx (2)
1-6: LGTM! Runtime and theme imports correctly migrated to scoped packages.The import path updates from
'rspress/runtime'and'rspress/theme'to'@rspress/core/runtime'and'@rspress/core/theme'are consistent with the dependency upgrade pattern.
26-26: LGTM! Re-export statement correctly updated.The re-export from
'@rspress/core/theme'maintains API compatibility while using the new scoped package structure.package.json (4)
61-61: Semver union (||) is acceptable—just double-check tooling support
The^8.19.4 || ^9.2.0range is valid SemVer, but some ancillary tooling (e.g., outdated lock-file auditors) occasionally mis-parses the||syntax. Verify that:
yarn installfinishes without warnings, andyarn constraints/yarn dedupestill agree with the new range.If any of those complain, consider falling back to a single caret range on the highest supported major.
93-93: Patch bump ofopenailooks safe
5.10.2is a patch-level release; no breaking API moves were announced. 👍
137-137:@swc/coreupgrade is fine but watch native binding rebuild time
Going from1.13.1→1.13.2should be ABI-compatible, yet CI caches might need a rebuild of native bindings. If the pipeline suddenly slows, clear the cache once.
70-73: No stale unscopedrspressimports found
A comprehensive ripgrep search for unscopedrspressin ES6 imports, import declarations, and CommonJS requires returned zero matches—your pinned @RsPress versions are safe.src/runtime/components/Overview.tsx (1)
1-6: Import migration looks correct—types kept separate from runtime code
Usingimport type { … } from '@rspress/core'keeps the bundle clean after tsc/SWC stripping. Good attention to tree-shaking concerns.
close #134
close #142
Summary by CodeRabbit
@rspress/coreand@rspress/core/themepackages, removing legacyrspressimports.@alauda/doom.@rspress/coremodule structure.