This topic contains 1 reply, has 0 voices, and was last updated by chanarbon 7 years, 4 months ago.

  • Author
    Posts
  • #18373

    david.smith

    Just pointing this out for everyone here in this group.

    2017.2 script changes that might affect your current code.

    Keep in mind that configuration of a require Object is optional. If you must configure a require Object,

    the @NAmdConfig tag is suited for general use. In limited cases, such as when you need run-time

    control over configuration options, use the require.config() method.

    As of 2017.2, you must update your existing scripts that call require Configuration. Scripts that use

    runtime calls of require Configuration throw an INVALID_AMD_CONFIG_PATH__1 error when:

    โ–  The call does not include the context property.

    โ–  The call includes the context property but its value is a path that conflicts with other entry point

    scripts.
    This is a cached copy. Click here to see the original post.

  • #18374

    chanarbon

    Yup. This is a must and everyone should need to take note for those who are using the old require.config() approach.

You must be logged in to reply to this topic.