Requested module 'fast-deep-equal' does not provide an export named 'default'
See original GitHub issueDescribe the bug
With version 0.9.79, there is something broken related to default exports, as I’m receiving this message in the console that breaks everything in my app:
The requested module '/node_modules/fast-deep-equal/index.js?v=dfdb27d1' does not provide an export named 'default'
It is fixed once I downgraded to 0.9.67
Issue Analytics
- State:
- Created a year ago
- Reactions:14
- Comments:17
Top Results From Across the Web
"The requested module ' does not provide an export named ...
"The requested module ' does not provide an export named 'default' " error, but only in relative import · I'm going to guess...
Read more >Requested module does not provide export named 'default'
To solve the error "The requested module does not provide an export named default", use the `default` keyword when exporting a value from...
Read more >does not provide an export named 'default' vue3 - You.com
The thing you want to do is import vue but it doesnot have a default export function or either the default thing to...
Read more >How to Solve does not provide an export named 'default'
To solve the error 'does not provide an export name default' in JavaScript, use the default keyword ... SyntaxError: The requested module '....
Read more >[Express.js] [node.js] Express.js server will not start because a ...
SyntaxError : The requested module './api/mflix.route.js' does not provide an export named 'default'. I read that this error can be caused ...
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
Downgrade to
v0.9.67
, you just need to set the exact version in yourpackage.json
, delete thenode_modules
directory and runnpm install
again.Its working in
v3.1.3
for me as well, thank you so much!Is it confirmed that it is this the expected behavior? I believe we need a confirmation by @fawmi that this repo is still being maintaned. This was the best Google Maps repo I found and it would be awesome if you guys keep it up with it.