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.
NoConflict() compatibility
See original GitHub issueThanks for making this project!
Could you wrap your whole code in
jQuery( document ).ready(function( $ ) { // Code that uses jQuery's $ can follow here. });
to enable noConflict() compatibility? When I include jQuery and then formBuilder, I get a “$ is not defined” error because I am in a noConflict() environment.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
jQuery.noConflict() | jQuery API Documentation
If for some reason two versions of jQuery are loaded (which is not recommended), calling $.noConflict( true ) from the second version will...
Read more >jQuery noConflict compatibility · Issue #2947 · select2 ... - GitHub
The last line, where $.fn.select2.amd is declared, should be jQuery.fn.select2.amd to avoid breakage when jQuery is in noConflict mode.
Read more >3325 (ui - not compatible with jQuery.noConflict())
Hello,. it seems that ui is not compatible with jquery.noConflict();. I use something like this: var $j = jQuery.noConflict();.
Read more >Correct way of loading non-AMD compatible jQuery plugins in ...
Using jQuery.noConflict(true) removes the jQuery global variable. When your plugin loads, it tries to access jQuery , but can't, ...
Read more >jQuery The noConflict() Method - W3Schools
The noConflict() method releases the hold on the $ shortcut identifier, so that other scripts can use it. You can of course still...
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
plugin output is now wrapper in an iife as of 2.10.4
Yes - the source is contained in many files which are joined together by webpack & minified. Putting every piece of code in its own IIFE would be both cumbersome & cause problems with namespaces / scoping.