Closed mjmnagy closed 4 years ago
Due to lazy loading child components
import autoStat from '@inputs/shared/status/auto'
export default {
components: {
autoStat //works
hiddenStat: () => import('@inputs/shared/status/hidden') //doesnt work
},
}
Due to lazy loading child components
import autoStat from '@inputs/shared/status/auto' export default { components: { autoStat //works hiddenStat: () => import('@inputs/shared/status/hidden') //doesnt work }, }
@mjmnagy, how did you solve the problem?
Due to lazy loading child components
import autoStat from '@inputs/shared/status/auto' export default { components: { autoStat //works hiddenStat: () => import('@inputs/shared/status/hidden') //doesnt work }, }
@mjmnagy, how did you solve the problem?
import hiddenStat from '@inputs/shared/status/hidden'
The lazy imports did not ever work for me
Version
5.0.0
Reproduction link
https://github.com/mjmnagy/error-sept-10-2020
Steps to reproduce
What is expected?
load the mixin into the file
Within a component you will have child components like to
To be included in the rolled up files
What is actually happening?
Update Aliases have been added to all these child component to enable absolute paths instead of relative.
entry.js
-> entry for rollup does not include or mention the child components as they are not supposed to be global or individually exposed outside of their parent component.Having the child component in the mixin or outside actually has no baring.
Added packages rollup-plugin-node-resolve rollup-plugin-local-resolve
Nada
Ive been browsing the options for the plugin and do not see anything relating to child components expect maybe
customBlocks
<- If this is the option would you need to add each child(which are not globally available)?