-
Notifications
You must be signed in to change notification settings - Fork 187
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
ArgHandler error on Webpack/UglifyJS build #74
Comments
I'm going to close this since I can't reproduce. Please reopen if you can provide more detail. |
Hi, I am actually running into the above issue, and I am not sure how to solve it. Here is the error that I am getting: ERROR in app-9c9bcdfb7ba5099216d1.js from UglifyJs I am able to run npm run buildlib, but when I run npm run build I get this error. I updated the webpack config with: node: {fs: 'empty'} This got rid of the initial error that allowed me to work with the library. For my index.js I am using the following to access xlsx-populate: import * as XlsxPopulate from 'xlsx-populate' I am using typescript which is why I am using that syntax. Any help would be greatly appreciated, thanks! |
Never mind, after digging a bit deeper I found my problem, in a previous question. If anyone else is having this issue, what solved it for me was updating the import statement to the following: import * as XlsxPopulate from 'xlsx-populate/browser/xlsx-populate'; Thanks for the help! |
@vickdayaram worked for me too. Thanks! |
Using the latest versions of
NodeJS
VueJS
Webpack
xlsx-populate
When running the build option we get an error on the pages including xlsx-populate.

We also got a 'Can't resolve fs' error on the dev build. We fixed this by adding the following to the webpack config:
node: {
fs: 'empty',
}
This solution was provided for the same issue in another package:
webpack-contrib/css-loader#447
Could these 2 issues be related to each other?
Steps to reproduce:
Setup new project using the vue-cli (default webpack project)
Install xlsx-populate
run 'npm run build' to create the production files. This should give you the error(s).
Or download the zip with sample project (without node_modules folder).
test.zip
And run 'npm install' followed by 'npm run build'
The text was updated successfully, but these errors were encountered: