signIn API + feature events

lib/build/components/superTokensRoute.js

@@ -88,16 +88,6 @@ function _interopRequireWildcard(obj) {
 /*
  * Imports.
  */
-
-/*
- * SuperTokensRouteWithRecipeId
- * Using react-router-dom, we can only match based on the route and not on the combination of path and query params.
- * having one route per component would lead to clashes when two components have the same route but different recipeId,
- * the first one would always take precedence.
- * Hence, the component rendered in the Route is an abstraction that decides which Feature to render based
- * on the rId.
- * See SuperTokensRouteWithRecipeId below.
- */
 function getSuperTokensRoutesForReactRouterDom() {
     try {
         var pathsToComponentWithRecipeIdMap = _superTokens["default"].getPathsToComponentWithRecipeIdMap();
@@ -108,21 +98,24 @@ function getSuperTokensRoutesForReactRouterDom() {
             });
         });
     } catch (e) {
+        // If react-router-dom is absent from dependencies, return [];
         return [];
     }
 }
 
-function SuperTokensRouteWithRecipeId(props) {
+function SuperTokensRouteWithRecipeId(_ref) {
+    var path = _ref.path;
+
     var Route = require("react-router-dom").Route;
 
     var recipeId = (0, _utils.getRecipeIdFromSearch)(window.location.search);
 
-    var component = _superTokens["default"].getMatchingComponentForRouteAndRecipeId(props.path, recipeId);
+    var component = _superTokens["default"].getMatchingComponentForRouteAndRecipeId(path, recipeId);
 
     return /*#__PURE__*/ React.createElement(Route, {
         exact: true,
-        key: "st-".concat(props.path),
-        path: props.path,
+        key: "st-".concat(path),
+        path: path,
         component: component
     });
 }