Viewing 1 replies (of 1 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    It looks like all of these warnings happen because the browser automatically tries to load JS/CSS source maps when you open the developer console and the plugin does not include those source maps.

    Source maps (JavaScript, CSS) are only used for development and debugging. They’re not necessary to actually run the plugin so I haven’t added them to the plugin repository. As far as I know, the browser won’t even try to load .map files unless you open developer tools, so this should have no performance impact one way or another.

    Note: While the plugin doesn’t include source maps, it does include the source code from which those maps can be automatically generated.

    • This reply was modified 5 years, 9 months ago by Janis Elsts.
Viewing 1 replies (of 1 total)

The topic ‘Backend Errors with plugin on version 1.9.6’ is closed to new replies.