Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Emitted value instead of an instance of Error
See original GitHub issueHello.
I am having this warning in the console, if anyone could check it out. I might send a PR, but not at this time.
(Emitted value instead of an instance of Error) autoprefixer: /node_modules/@trendmicro/react-dropdown/dist/react-dropdown.css:172:3: You should write display: flex by final spec instead of display: boxIssue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
`angular` how to fix this warning `Emitted value instead of an ...
Add '/' to the beginning of the path: example:'/assets/images/logo.png' where assets is located in the root under src Folder.
Read more >WARNING in '...' (Emitted Value instead of an instance of Error ...
This seems to happen for any file where I reference a background image in css.
Read more >Emitted value instead of an instance of Error - Vue Forum
i'm doing a simple loop inside a vue component but i keep getting this error ERROR in ./node_modules/vue-loader/lib/template-compiler?
Read more >Vue项目中解决Emitted value instead of an instance of Error问题
(Emitted value instead of an instance of Error) <van-cell v-for=" item in this.todoList">: component lists rendered with v-for should have ...
Read more >前端开发：Vue项目中解决Emitted value instead of an instance ...
(Emitted value instead of an instance of Error) <van-cell v-for=" item in this.todoList">: component lists rendered with v-for should have ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed in v1.2.2
I am not sure either. Couldn’t find anything on Google.
However, I looked a bit deeper in the warning and found something. I don’t think that this has anything to do with file being prefixed multiple times. It has to do something with final specification for the display property.
I guess you should update autoprefixer to the latest version and run build again.
Please, have a look at this: https://github.com/postcss/autoprefixer#warnings
Edit: I forgot to mention that I didn’t see this warning in 1.2.0 version.