Error on importing from browser console
See original GitHub issueVersion: 0.4.1 from jsDelivr
I just tried
(await import('https://cdn.jsdelivr.net/npm/@js-temporal/polyfill@0.4.1/dist/index.esm.js')).Temporal
to import polyfill in browser console, but I got:
Uncaught TypeError: Failed to resolve module specifier "jsbi". Relative references must start with either "/", "./", or "../".
Issue Analytics
- State:
- Created a year ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Console error on import of non-existent file in vite
I am migrating from webpack using Vue2.7 and @vitejs/plugin-vue2. So there was one problem. await import(`${path} ...
Read more >Error when dynamically importing tf.js from browser console
Simply run import('https://cdn.jsdelivr.net/npm/@tensorflow/tfjs@0.12.0').then((tf) => {}) in your chrome console.
Read more >Error after deploying application on browser console - Support
As the error states, when using import in a browser context you need to use a relative reference e.g. import wA from "./lodash/assign";....
Read more >Using the Debug Console in Google Chrome to identify errors
Google Chrome's Debug console is a powerful tool that can help us identify the cause of the errors (displayed in red) and speed...
Read more >Console messages — Firefox Source Docs documentation
The Web Console understands source maps. This means that if your JavaScript sources are compressed, you can supply a source map for them....
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
FWIW you can use the experimental rewrite support on unpkg: https://unpkg.com/@js-temporal/polyfill@0.4.1/dist/index.esm.js?module
Closing due to inactivity, and there’s multiple potential solutions provided.