-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with Vue scoped dynamic slots when using @rollup/plugin-alias
#445
Comments
Some additional information. I was messing around with removing the use of rollup.config.js, and was trying something unrelated. Instead of the rollup config, I used vite to build instead of rollup, and I didn't get the error. Why it works via vite, but not rollup, I have no idea.
vite.config.ts |
Maybe plugin order matters? In your second config you have typescript() after vue(). |
I just messed around with the order a bit, but nothing changed. BUT... when I was stripping things down to match my vite config (more updated than posted above), it appears that Specifically when I have it set to: alias({
entries: [
{ find: '@', replacement: 'src' },
]
}), Additionally, if I change it to something like the following, the same problem exists. alias({
entries: [
{ find: '@plugin', replacement: 'src/plugin' },
]
}), I tried other ways of using that plugin with entries as an object, that had the same problem. If I change the find value to anything that doesn't actually resolve anything (ex. Originally I thought the For reference, I added a new vite config for the build script to use (I'm using the regular one for the docs pages already). This is what it has, and seems to be working as expected. Granted I have yet to actually test it as an npm package as it's wip, but the build does pass. If you want to see any other changes, my dev branch is the most up to date now.
vite.build.config.ts |
@rollup/plugin-alias
Troubleshooting
Does
tsc
have the same output?No
Does your Rollup plugin order match this plugin's compatibility?
Yes
Can you create a minimal example that reproduces this behavior?
This is the project repository I'm having this issue with: https://github.com/webdevnerdstuff/vuetify-drilldown-table
What happens and why it is incorrect
When trying to bundle the code, I'm getting this error output. The code works as expected when running in development under vite (
pnpm play
if you are checking out the repo). The error is almost identical to what is happening in this issue: #325 Except in my case I'm using@vitejs/plugin-vue
not the depreciated packagerollup-plugin-vue
. Perhaps it's the same issue? The other issue didn't really have a resolution, so I'm a bit stuck at the moment and don't know what to do. Any help is greatly appreciated at this point as my experience with ts/rollup is relatively new'ish, and I've been stuck trying to figure this out for over a week now.In the repo example I gave, you can see the code in the
VDrilldownTable.vue
file at line 190. I also tried doing the same thing a different way (pretty much does the same thing) at line 201. They both produce the same error.Environment
Versions
:rollup.config.js
https://github.com/webdevnerdstuff/vuetify-drilldown-table/blob/main/rollup.config.js
https://github.com/webdevnerdstuff/vuetify-drilldown-table/blob/main/tsconfig.json
:tsconfig.json
https://github.com/webdevnerdstuff/vuetify-drilldown-table/blob/main/package.json
:package.json
plugin output with verbosity 3
:The text was updated successfully, but these errors were encountered: