Scripts are treated as modules, when they aren't.
See original GitHub issueWith version 3.0.0, all <script>
tags are treated as modules, when they might not be.
This causes no-undef rules to fail when they currently are fine in the browser.
Is it possible to limit the new functionality to modules only or something?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:13 (6 by maintainers)
Top Results From Across the Web
JavaScript modules - MDN Web Docs
This guide gives you all you need to get started with JavaScript module syntax.
Read more >Javascript module not working in browser? - Stack Overflow
Using JS modules in the browser On the web, you can tell browsers to treat a element as a module by ...
Read more >ModuleScripts Discussion - Scripting Support
It is advisable to treat modules as libraries for specific functionalities. That said, it is perfectly fine but you need to convert some...
Read more >Modules • JavaScript for impatient programmers (ES2022 ...
Scripts are code fragments that browsers run in global scope. They are precursors of modules. CommonJS modules are a module format that is...
Read more >ECMAScript modules in browsers - JakeArchibald.com
All you need is type=module on the script element, and the browser will treat the inline or external script as an ECMAScript module....
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
Okay I published a
alpha.1
version. It should fix your issue with spaced-comment because it doesn’t use comments anymore.Sorry for the wait. I just released the v4, as I can’t think of any issue. Let me know how it works for you!