Error: Not Supported
See original GitHub issueTrying to upgrade to @^15, but we’re getting an odd stack trace with Error: Not Supported
when trying to run our tests with jest. (The error also exists in 14.4.0, but not with the last 13.x release)
In version 14.4.0 the line number points to index.umd.js:872
which is the import statement inside this block, but in version 15.0.1 its now line 1012 (but the same exact block of code):
if (typeof window !== 'undefined') {
import('details-element-polyfill');
}
It looks like an errant import
statement is escaping whatever transforms are being applied to the UMD file for loading into node.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
not supported error when I try and import local module - Stack ...
I have a local module (speech.js) in my create-react-app src folder that is the google text to speech code on their website. I...
Read more >Dynamic import fails with "Error: Not Supported" #2283 - GitHub
I use Ava for tests and (only during tests) i got the error message Error: not supported . After some research it turned...
Read more >Error: Not Supported - Dave Lage
If you are working with Node.js 12.x which adds full ESModule support, you may find you run into this error. This occurs using...
Read more >Fixing “This Plugin is Not Supported” error in Windows 10/11
1. Enable Flash in Chrome. 2. Install the latest Flash player; Update Flash:Clear the browsing data in Chrome. 3. Use another browser to...
Read more >How to Fix Request Method 'POST' Not Supported - Hyperping
The Request Method' POST' Not Supported' is an HTTP response status. The error prompt shows that a request to access your website has...
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 FreeTop 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
Top GitHub Comments
Fixed in #642 - should be releasing 15.1.0 - sorry for the wait y’all! 🙏
Was running into the same exact issue. Doing the following swap got it working for me.
import('details-element-polyfill')
=>require('details-element-polyfill').default
At first, I tried adding the babel-plugin-dynamic-import-node plugin, but that didn’t seem to make a difference in the
dist
build.