Replies: 1 comment
-
|
Small update: I noticed that removing In diff --git a/tsconfig.vitest.json b/tsconfig.vitest.json
index 571995d..f29bf66 100644
--- a/tsconfig.vitest.json
+++ b/tsconfig.vitest.json
@@ -6,6 +6,6 @@
"tsBuildInfoFile": "./node_modules/.tmp/tsconfig.vitest.tsbuildinfo",
"lib": [],
- "types": ["node", "jsdom"]
+ "types": ["node"]
}
}Along with the following change in diff --git a/tsconfig.app.json b/tsconfig.app.json
index 93f952f..25a0e9f 100644
--- a/tsconfig.app.json
+++ b/tsconfig.app.json
@@ -3,7 +3,7 @@
"include": ["env.d.ts", "src/**/*", "src/**/*.vue"],
"exclude": ["src/**/__tests__/*"],
"compilerOptions": {
- "composite": true,
+ "composite": false,
"tsBuildInfoFile": "./node_modules/.tmp/tsconfig.app.tsbuildinfo",
"paths": {But that's most likely not the right fix to the problem |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello there,
I'm not sure if this qualifies as a bug - this might be something wrong with my setup.
I'm trying to build a simple internal component library using shadcn-vue. I have a fairly simple setup, basically just a few components from shadcn without any modification yet.
I'm trying to build a library target. If I run
build-onlythe app builds "fine" - as in it's completely usable, I can import it in my other projects.The issue is when I try to use
yarn build, as it seems to fail in the type checking. This is reproducible by running bothyarn buildandyarn type-check:This happens on a lot of components that I have from shadcn. I created a sample repository that reproduces the issue - basically a copy of my library, just with only one component - the
sheet.Links:
I would greatly appreciate any help. I would love to understand what I did wrong and how did I end up with this error.
Beta Was this translation helpful? Give feedback.
All reactions