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
Can't resolve 'fs' in xlsx-style #16
Comments
same issue |
any solution? |
Facing same issue in Angular 6 project. Any solution for this? |
same issue. |
Same issue, any solution??? |
Hi, I've solved my problem with another library. https://github.com/guyonroche/exceljs#styles Your code sample is this source good luck |
Facing the same issue with Angular 6, any solution ? |
Any solutions found? (aside from switching to a different module) |
same issue with Angular 7, any solution ? |
`WARNING in ./node_modules/xlsx-style/xlsx.js to solve this issue , i modified source code of 'xlsx-style/dist/cpexcel.js' from ERROR in ./node_modules/xlsx-style/xlsx.js for these two issues , i solved by adding node attribute to 'webpack.config.js',like this node: {
fs: "empty"
} One passible reason here is the webpack treat 'fs' as package module but not node module |
in my project webpack.config.js doesnt exist. how can i fix it ? |
这里说的是自己项目的webpack.confog.js,而不是xlsx-style的,你可以自己在项目根目录新建一个webpack.config.js,让你在打包的时候自动正确识别fs。 |
Did you find any solutions? |
Hi,
I'm using angular 6 and I can export json data with XLSX using ngx-excel-export.
When I try to style the exported excel document through xlsx-style, I get building errors:
`WARNING in ./node_modules/xlsx-style/xlsx.js
Module not found: Error: Can't resolve 'crypto' in 'D:\Web\node_modules\xlsx-style'
ERROR in ./node_modules/xlsx-style/xlsx.js
Module not found: Error: Can't resolve 'fs' in 'D:\Web\node_modules\xlsx-style'
ERROR in ./node_modules/xlsx-style/ods.js
Module not found: Error: Can't resolve 'fs' in 'D:\Web\node_modules\xlsx-style'`
How can I solve that?
Thanks
PS: I'm not using node or webpack, it's a simple angular application.
The text was updated successfully, but these errors were encountered: