Conversation
… setup - Fixed shadcn.ts to properly discover UI components from Nuxt layer packages - Updated shadcn module to search node_modules for @pleaseai/docs-layer when resolving components - Modified templates to use UiSeparator prefix for component references - Added missing return type annotations to utils and composables (ESLint compliance) - Added content components for documentation rendering - Updated nuxt.config.ts shadcn configuration for layer compatibility - Fixed process import in utils/git.ts for node environment This resolves component resolution issues in multi-layer Nuxt setups where UI components are defined in the layer package but need to be discovered at runtime.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
docs-please | 7f2af98 | Dec 02 2025, 12:53 AM |
…layer setup - Add useNuxt() to content.config.ts to resolve app's content directory - Register content components globally via components:dirs hook - Add CopyButton, CodeBlockCommand components and Icons.ts from shadcn-vue - Add tooltip UI components via shadcn-vue CLI - Add useConfig composable for package manager preference - Fix container utility class definition for Tailwind CSS v4 - Add @tabler/icons-vue dependency for icon components
Deploying docs-please with
|
| Latest commit: |
7f2af98
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b61ed963.docs-please.pages.dev |
| Branch Preview URL: | https://fix-layer-component-resoluti.docs-please.pages.dev |
…layer setup - Register app/components/app and app/components/docs directories explicitly - Fix CSS module to import main.css after @source directives - Remove duplicate tailwindcss import from main.css - Use @Utility directive for container class (Tailwind v4 syntax) - Add exsolve dependency for module path resolution
- Keep component registration hooks for app, docs, content directories - Use main's updated component implementations - Preserve exsolve dependency and CSS module changes - Update landing page to main's new design
This was referenced Dec 3, 2025
Closed
Closed
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes component resolution issues in multi-layer Nuxt setups where UI components are defined in the layer package but need to be discovered at runtime.
Key Changes
Core Fix:
/packages/layer/modules/shadcn.ts- Enhanced layer component discovery logic/packages/layer/nuxt.config.ts- Updated shadcn module configurationUI Components Added:
ESLint Compliance:
/packages/layer/utils/git.ts/packages/layer/utils/meta.ts/packages/layer/app/composables/useNavigation.tsDocumentation Updates:
Test Plan
bun lint:fixcd packages/layer && bun typecheckbun buildbun devand test component rendering