Skip to content

Using options throws error: parseQuery should get a string as first argument #707

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

Closed
dim882 opened this issue May 1, 2018 · 1 comment · Fixed by #810
Closed

Using options throws error: parseQuery should get a string as first argument #707

dim882 opened this issue May 1, 2018 · 1 comment · Fixed by #810

Comments

@dim882
Copy link

dim882 commented May 1, 2018

Do you want to request a feature or report a bug?
Report a bug

What is the current behavior?
Using options throws the error:

   Module build failed: Error: parseQuery should get a string as first argument
        at Object.parseQuery (/path/to/app/node_modules/loader-utils/index.js:68:9)
        at Object.module.exports (/path/to/app/node_modules/css-loader/lib/loader.js:1

If the current behavior is a bug, please provide the steps to reproduce.

https://gist.github.com/mrdanimal/a49acbb6fcdcb4b44171db4675b769ba

What is the expected behavior?
It should allow you to configure the loader using options

Please mention other relevant information such as your webpack version, Node.js version and Operating System.

  • webpack version: 4.6.0
  • node version: 9.11.1
  • OS: MacOS 10.12.6
@alexander-akait
Copy link
Member

@mrdanimal Looks like a bug, feel free to fix and send PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants