0.2.0 - Mid migration

web/node_modules/@material-ui/styles/createStyles/createStyles.d.ts

@@ -0,0 +1,16 @@
+import { StyleRules } from '@material-ui/styles/withStyles';
+
+/**
+ * This function doesn't really "do anything" at runtime, it's just the identity
+ * function. Its only purpose is to defeat TypeScript's type widening when providing
+ * style rules to `withStyles` which are a function of the `Theme`.
+ *
+ * @param styles a set of style mappings
+ * @returns the same styles that were passed in
+ */
+// For TypeScript v3.5 Props has to extend {} instead of object
+// See https://github.com/mui-org/material-ui/issues/15942
+// and https://github.com/microsoft/TypeScript/issues/31735
+export default function createStyles<ClassKey extends string, Props extends {}>(
+  styles: StyleRules<Props, ClassKey>
+): StyleRules<Props, ClassKey>;

web/node_modules/@material-ui/styles/createStyles/createStyles.js

@@ -0,0 +1,10 @@
+"use strict";
+
+Object.defineProperty(exports, "__esModule", {
+  value: true
+});
+exports.default = createStyles;
+
+function createStyles(styles) {
+  return styles;
+}

web/node_modules/@material-ui/styles/createStyles/index.d.ts

@@ -0,0 +1,2 @@
+export { default } from './createStyles';
+export * from './createStyles';

web/node_modules/@material-ui/styles/createStyles/index.js

@@ -0,0 +1,15 @@
+"use strict";
+
+var _interopRequireDefault = require("@babel/runtime/helpers/interopRequireDefault");
+
+Object.defineProperty(exports, "__esModule", {
+  value: true
+});
+Object.defineProperty(exports, "default", {
+  enumerable: true,
+  get: function get() {
+    return _createStyles.default;
+  }
+});
+
+var _createStyles = _interopRequireDefault(require("./createStyles"));

web/node_modules/@material-ui/styles/createStyles/package.json

@@ -0,0 +1,5 @@
+{
+  "sideEffects": false,
+  "module": "../esm/createStyles/index.js",
+  "typings": "./index.d.ts"
+}