framer-motion 6.3.12 → 6.3.13

package/dist/cjs/index.js

@@ -472,7 +472,7 @@ var MotionValue = /** @class */ (function () {
          * This will be replaced by the build step with the latest version number.
          * When MotionValues are provided to motion components, warn if versions are mixed.
          */
-        this.version = "6.3.12";
+        this.version = "6.3.13";
         /**
          * Duration, in milliseconds, since last updating frame.
          *
@@ -599,7 +599,7 @@ var MotionValue = /** @class */ (function () {
      * }
      * ```
      *
-     * @internalremarks
+     * @privateRemarks
      *
      * We could look into a `useOnChange` hook if the above lifecycle management proves confusing.
      *
@@ -3444,7 +3444,7 @@ function useHTMLProps(props, visualState, isStatic) {
 /**
  * A list of all valid MotionProps.
  *
- * @internalremarks
+ * @privateRemarks
  * This doesn't throw if a `MotionProp` name is missing - it should.
  */
 var validMotionProps = new Set([
@@ -5864,7 +5864,7 @@ function useDrag(props) {
  * @param handlers -
  * @param ref -
  *
- * @internalremarks
+ * @privateRemarks
  * Currently this sets new pan gesture functions every render. The memo route has been explored
  * in the past but ultimately we're still creating new functions every render. An optimisation
  * to explore is creating the pan gestures and loading them into a `ref`.
@@ -5966,7 +5966,7 @@ function updateMotionValuesFromProps(element, next, prev) {
              * and warn against mismatches.
              */
             if (process.env.NODE_ENV === "development") {
-                warnOnce(nextValue.version === "6.3.12", "Attempting to mix Framer Motion versions ".concat(nextValue.version, " with 6.3.12 may not work as expected."));
+                warnOnce(nextValue.version === "6.3.13", "Attempting to mix Framer Motion versions ".concat(nextValue.version, " with 6.3.13 may not work as expected."));
             }
         }
         else if (isMotionValue(prevValue)) {

package/dist/es/gestures/use-pan-gesture.mjs

@@ -9,7 +9,7 @@ import { PanSession } from './PanSession.mjs';
  * @param handlers -
  * @param ref -
  *
- * @internalremarks
+ * @privateRemarks
  * Currently this sets new pan gesture functions every render. The memo route has been explored
  * in the past but ultimately we're still creating new functions every render. An optimisation
  * to explore is creating the pan gestures and loading them into a `ref`.

package/dist/es/motion/utils/valid-prop.mjs

@@ -1,7 +1,7 @@
 /**
  * A list of all valid MotionProps.
  *
- * @internalremarks
+ * @privateRemarks
  * This doesn't throw if a `MotionProp` name is missing - it should.
  */
 var validMotionProps = new Set([

package/dist/es/render/utils/motion-values.mjs

@@ -18,7 +18,7 @@ function updateMotionValuesFromProps(element, next, prev) {
              * and warn against mismatches.
              */
             if (process.env.NODE_ENV === "development") {
-                warnOnce(nextValue.version === "6.3.12", "Attempting to mix Framer Motion versions ".concat(nextValue.version, " with 6.3.12 may not work as expected."));
+                warnOnce(nextValue.version === "6.3.13", "Attempting to mix Framer Motion versions ".concat(nextValue.version, " with 6.3.13 may not work as expected."));
             }
         }
         else if (isMotionValue(prevValue)) {

package/dist/es/value/index.mjs

@@ -25,7 +25,7 @@ var MotionValue = /** @class */ (function () {
          * This will be replaced by the build step with the latest version number.
          * When MotionValues are provided to motion components, warn if versions are mixed.
          */
-        this.version = "6.3.12";
+        this.version = "6.3.13";
         /**
          * Duration, in milliseconds, since last updating frame.
          *
@@ -152,7 +152,7 @@ var MotionValue = /** @class */ (function () {
      * }
      * ```
      *
-     * @internalremarks
+     * @privateRemarks
      *
      * We could look into a `useOnChange` hook if the above lifecycle management proves confusing.
      *

package/dist/framer-motion.dev.js

@@ -1706,7 +1706,7 @@
              * This will be replaced by the build step with the latest version number.
              * When MotionValues are provided to motion components, warn if versions are mixed.
              */
-            this.version = "6.3.12";
+            this.version = "6.3.13";
             /**
              * Duration, in milliseconds, since last updating frame.
              *
@@ -1833,7 +1833,7 @@
          * }
          * ```
          *
-         * @internalremarks
+         * @privateRemarks
          *
          * We could look into a `useOnChange` hook if the above lifecycle management proves confusing.
          *
@@ -4678,7 +4678,7 @@
     /**
      * A list of all valid MotionProps.
      *
-     * @internalremarks
+     * @privateRemarks
      * This doesn't throw if a `MotionProp` name is missing - it should.
      */
     var validMotionProps = new Set([
@@ -7098,7 +7098,7 @@
      * @param handlers -
      * @param ref -
      *
-     * @internalremarks
+     * @privateRemarks
      * Currently this sets new pan gesture functions every render. The memo route has been explored
      * in the past but ultimately we're still creating new functions every render. An optimisation
      * to explore is creating the pan gestures and loading them into a `ref`.
@@ -7200,7 +7200,7 @@
                  * and warn against mismatches.
                  */
                 {
-                    warnOnce(nextValue.version === "6.3.12", "Attempting to mix Framer Motion versions ".concat(nextValue.version, " with 6.3.12 may not work as expected."));
+                    warnOnce(nextValue.version === "6.3.13", "Attempting to mix Framer Motion versions ".concat(nextValue.version, " with 6.3.13 may not work as expected."));
                 }
             }
             else if (isMotionValue(prevValue)) {