-
-
Notifications
You must be signed in to change notification settings - Fork 153
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
[Bug] partialBundling causes an error in the build product #769
Comments
In import * as wavyUnderline from './components/wavyUnderline'
interface Component {
css: string
html: string
}
export default [wavyUnderline] as Component[] |
use and |
works |
try set |
Set groups and targetMinSize
set
|
my mistake, you can set |
Three components and three output files. This works. But it seems there is still something wrong with Test should be correct now.
|
I'll check |
This may be a issue related to bundling, I'll look into it |
I found the reason, it will be fixed in |
This is not fixed in |
I'll try, it works with my examples |
I'll make farm runtime not affect by this option in 0.14.5 too. |
fixed in |
This is fixed. |
Steps to reproduce
Open the console.
The output:
In
/home/niuiic/Documents/projects/gallery/apps/website/src/view/page/main/Main.tsx
cssComponents
is{}
In
/home/niuiic/Documents/projects/gallery/packages/css/farm.config.build.ts
Unset
partialBundling
, thencssComponents
is an array with one item.enforceResources
is set to[{ name: 'wavyUnderline', test: [ 'src/components/wavyUnderline/*' ] }]
.What is expected?
The output
What is actually happening?
{}
System Info
System: OS: Linux 6.1 Gentoo Linux CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics Memory: 12.92 GB / 15.59 GB Container: Yes Shell: 5.9 - /bin/zsh Binaries: Node: 21.1.0 - /run/user/1000/fnm_multishells/11955_1700613217468/bin/node npm: 10.2.0 - /run/user/1000/fnm_multishells/11955_1700613217468/bin/npm pnpm: 8.10.5 - /run/user/1000/fnm_multishells/11955_1700613217468/bin/pnpm npmPackages: @farmfe/core: ^0.14.3 => 0.14.3
The text was updated successfully, but these errors were encountered: