Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8390803
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T19:06:03+00:00 2026-06-09T19:06:03+00:00

When using ExtJS 4+ with asynchronous loading one would be familiar with this sort

  • 0

When using ExtJS 4+ with asynchronous loading one would be familiar with this sort of warning:

[Ext.Loader] Synchronously loading 'MY.particular.module';
consider adding Ext.require('MY.particular.module') above Ext.onReady

How to identify which JavaScript module (be it a controller, a component, etc) is causing this warning? I.e. the place where include module being synchronously loaded in the requires list.

What is the right way to go around correcting these warnings? Does an automated way to do this exist?

P.S. The only way to do this right now, is to set a debug point where the warning is raised, and trace back to which line in which file is leading to the warning being generated.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T19:06:04+00:00Added an answer on June 9, 2026 at 7:06 pm

    In chrome, in your stacktrace, (I think Firefox does stacktraces as well nowadays?) the file that is calling in a module is usually (always?) the 1st file that is not ext-all.

    Ext.require is something used TO automate stuff ( eg js-minification) so you can’t really automate it in and of itself.

    When you declare a component ( using Ext.define or Ext.create ) you should be specifying the modules the component that Ext is going to use for the component with Ext.require ( well, if you want to get rid of this warning atleast )

    Every custom component that you are using should more or less follow the same idea:

    Ext.define('My.app.Panel', {
        extend: 'Ext.panel.Panel', // 
        requires: [
            'My.app.PanelPart2', //Hey! warning is gone!
            'My.app.PanelPart3'
        ]
    
        constructor: function (config) {
            this.callParent(arguments); 
            //...
        },
    
        statics: {
            method: function () {
                return 'abc';
            }
        }
    });
    

    And if you don’t care about performance, and only want to get rid of stray warnings ( insanity technically, you can just muck your error message, in the loader config .

    Ext.loader.setConfig({
      enabled: true,
      paths: {
          'My': 'my_own_path'
      },
      onError:function(){}//or custom handler? :D
    

    See mitchsimeons answer: http://www.sencha.com/forum/showthread.php?178888-Tons-of-Synchronously-Loading-Warning-Messages

    and a blog post on why requires:
    http://www.sencha.com/blog/using-ext-loader-for-your-application

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm using ExtJS to create a formPanel: new Ext.FormPanel({ labelAlign: 'top', title: 'Loading Contact...',
I am using extjs textfield in one of the grids in a webpage. This
I am using extjs version 3.4 and I am getting one error in this
Using ExtJS 4.0.2 , I can type the following into the console: Ext.util.Format.date('2012-01-13', m-d-Y);
// Using extjs 3.x var box = new Ext.Textfield { /* textField configuration */
How do you implement a multiselect combobox as part of a Ext.FormPanel using ExtJs?
I'm using ExtJS 4.0.7, am new to Ext, and am using the new MVC
I'm using ExtJS 3.0 and I would like to extend FormPanel or any solution
I am using ExtJS 3 here. I would like to populate a formpanel from
I created a grid using extjs library. First created a model: Ext.define('Option', { extend:

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.