` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","_npmUser":{"name":"bonniez","email":"bonniez@google.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"5.6.0","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"_nodeVersion":"8.7.0","_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_0.35.0_1524523196109_0.13679149015658387","host":"s3://npm-registry-packages"}},"0.38.0":{"name":"@material/auto-init","version":"0.38.0","license":"Apache-2.0","_id":"@material/auto-init@0.38.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"0cff255825a030acdaece8518fc2fd2e67b5ab54","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-0.38.0.tgz","fileCount":5,"integrity":"sha512-s3p5ww4BhCI/ySUulV0TxlAUg9R4PMcFYNGa7Kx4SUoD8k+rai61pgFiJW16YfWbtaI+wCQ25zDFB7Ek3bdpuw==","signatures":[{"sig":"MEUCIE3wOE1dcNCHyXsfRzvsxXhkwoA99sj2q6gBhDhB1UEdAiEAiczaIedL+KB5i7o2BMgXJPbh1ywCrCmNIG+xeS7OTcw=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":18328,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbX0V9CRA9TVsSAnZWagAAy8IP/1TLoQo1uQyOAbghfM31\nU+Bxwh5iJHDgKX+Uff0KbIqWsIW5SbwJ/OS81RlAZQVbh5/qrnp0PFN96b1K\nEj/LWpBZgsRoHVG4Nfq4ZEzI+xkbgmMqxESf/HRz0uZ13mVzQtx/9JbxZG2q\nQ1K3kzMavmx2KkdUBo45ZF2QN7EfJ1yKcNhjKStAirRgrM73xfWHCRWjphxP\nNUiRG1tIhRt55mrNoF03/EXRCXBewuSK/UpLPB+xI3K4j+OVg82wslc1roF0\nxkhsewcFgnoIbSEK8Bgcg8T30vxErQBt7AJCvb0TqAaM7hxJNog42A0lIH6P\n3c7tOtuGQ6FfHgvFWyTqFEdmvSpLUTpGMemvdSL83/Hjszt8i4H/i038pZUk\n05FN2LBMD6/z8s2FgooUMy1qHruBUrGCiJIrvKvhMwLTSXkG0oZS5IQ40ZW/\nqAK006j1AaxKgPaU6bzM6JtqRQXxuFF/rZlLRDeTldVKcyuK1G/EZbrdWV8g\nrGAROAioMhwidmdPpuFfOsVOhxZPDFF4Jn/D4r/s8umNA4lUL7is4TaVWwxP\nfbpglwpD4byHsFis+i0FzGvkZBBnd/87gp5ceOF1Icb7JtFcqUlnX5GdlJYb\ns3n2oVelp4SZCyWYaijrLY5AJ2UNQxRUzZf6SW5yzERdU8C1OeE+dDo1xHZ4\nkwMa\r\n=Ronl\r\n-----END PGP SIGNATURE-----\r\n"},"main":"index.js","_npmUser":{"name":"acdvorak","email":"acdvorak@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"6.2.0","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"_nodeVersion":"9.11.1","_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/auto-init_0.38.0_1532970365098_0.2562643199897816","host":"s3://npm-registry-packages"}},"0.39.0":{"name":"@material/auto-init","version":"0.39.0","license":"MIT","_id":"@material/auto-init@0.39.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"9bf4af107ca18e1bd782a9ee12ace65c5b9b6399","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-0.39.0.tgz","fileCount":5,"integrity":"sha512-rh/YbGupzHiY9b3V/KFBzoEKcBCY8KDXQZNnNFZwP3fwDaaU6pSbVwg5jKfR6QfrQZF7AetdCYJj0p5UKDcvnA==","signatures":[{"sig":"MEQCIH9UW11ZxgN8+d9cITR4WJLLHctc3tfE6F7apL9iZd33AiAd7UFw5DyGxABf9Pt/I7gAMwgeAiZvYJplPk8kIE8fJA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":20446,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbhDdsCRA9TVsSAnZWagAA65cP+gNRniLDraRvxdDJq2Ez\n2UkxBdxx1w8CU5RRqFhs92R0OP+r16r+UFMZKiRnAnLjXI+0UZOHWNriRZpo\n8VddgNet3WNhvwN9e1bCY7RpPLbD1tHjmB5MA4N5JhsHPnl51VVyhL7cit+6\nFdasl1++yCoctSvHYjkvBR0DwsUwgimjfvm1DfmXed4tWoQXsQfqVUnlXhZW\nv2RNO1s4XS9ez5aY72uUggrTCbCN4hPyMvtieBjNfFFWH/O7dEYKPt5HnGVn\nGYpODQLQWmmvGlyNof6DqXByA8O8Nm61dn60Iwz2IGNHnOLTN6BMQJcKc2UM\nQ0cYnln0VmFzknjdLzkkrljyf7P4TA/TB4uzNYHLysJ/AdBJiUmTbGvojvk0\nb/WgUzzCDDPCLi1xKItnJFIWtgxhbLGSyf1dXMkzkHE1F+iPrZU88hm2tv3g\nMIu3nHmvio9Bg3XjE/9B2/ptb19naG1glBRIaUUD6mEq88uhzmCgNUa0f2be\nvW6binU+8A0lt/GRtDnfYY5inAQY8zY01W4tDgvA9D7gTiET8e8M1T9ModYc\nfj6eSJECOeAA7uEzFfwi2qIpMlhaPssyS37OzwO/65iwvHmpgUFk2ZLL6/sH\nT6/yRjdN56u3awaOqJTkqTgP1dVNE9OYG9lP6Hiwv2tBFhQdLkGzym7nOHuQ\nQbbw\r\n=Z/ov\r\n-----END PGP SIGNATURE-----\r\n"},"main":"index.js","_npmUser":{"name":"williamernest","email":"williamernest@google.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"6.3.0","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"_nodeVersion":"9.4.0","_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/auto-init_0.39.0_1535391595985_0.7128206143728129","host":"s3://npm-registry-packages"}},"0.41.0":{"name":"@material/auto-init","version":"0.41.0","license":"MIT","_id":"@material/auto-init@0.41.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"8a59bb0b83e0f51ead9508074f9a29b2b6a20eec","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-0.41.0.tgz","fileCount":5,"integrity":"sha512-jp6L8MpYu7DudgDfA8iTyD9BwQrYPEDsIJGbqzN9vcCBl5FoBatkB8pcFXKr+1mRBk7T1Qmf6+H5nDtxyXjHEQ==","signatures":[{"sig":"MEYCIQCcMZolPr4O/zYFLmXdirNI9L3eS9WwtINGXjZJl6zwygIhAPSZXiZAVD7OOFGe+ao8q4XSDHfpDeVvYIU8AWeMg0Xg","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":20458,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb12vMCRA9TVsSAnZWagAA85kP/2FF6mmHQG6HClS+KyQQ\ndDR6fkVQXytZbVY99uYJjgU7nT5wThIoaM5bJTSCJtvGvO2dd5KaL/HWzQs1\nq7+2JrKz/Au2OOMrcaKC+LKs5TV4mWWd3ZC4ghJWL6xRvu789ulgxBCuXElx\nMRhpNbGzM/c4VlyuO1A4T2+DZgRym4hkqPf8EhBt5gDeyPRbTkVOfqxQfNtZ\nx2Pp2sZ72kfG0XNiPS6YZBSATnX4MtNnNsqh8qvTSKHCA7edZkXDhhwDrX8X\nvnDicD8bOLntj072e3vFiLyUgMHFg7JbA5KotP7leqtpLeqZz6qiVJU4SpdF\nc1PKgo66sOHsPv7HF1BbcEYzWzI54J2pVNYxvV1RPOM5FsoaA2D1AnkXUdOW\nBIM2YZsgjT2k72WX5uGGzGuRvsHUoGPts4sJrdOdUqrVzgtrtMlHNZbAjhFs\nXHalUDyq4CYbnL/gbpse16bdx7oKxy+3RDR4+HSciIKKQZOK4z3dEjSluhX3\nS8IQGZe8aWZX3LAdxVqn9pAdCb3OIUKOjsVl5ePN8rcOorayzoIWW7I3CnKh\nv3qRIKQQ4FtThwJ5DOWpbBq58lwEMkMw0VQ3OadgMVaGqdv1vQlJFvzBKW5Y\nrcdMeYW34CuNaW0UWVDoJTQVqTThTIH3n6kl1E2e6F+uQ9vzEoLFGxT2GVZP\nqB/m\r\n=c8g7\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","_npmUser":{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"6.4.0","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"_nodeVersion":"8.11.1","_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/auto-init_0.41.0_1540844491866_0.663243635427341","host":"s3://npm-registry-packages"}},"1.0.0-0":{"name":"@material/auto-init","version":"1.0.0-0","license":"MIT","_id":"@material/auto-init@1.0.0-0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"9d9f1463a5e5066265c16b683fe923a4d003da51","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-1.0.0-0.tgz","fileCount":10,"integrity":"sha512-ABIew0LOQv+/Fnezu0vUQBjB1iJUyBwIANQOEIJeUspigzn4vjTk8nk64ceb11zzlEBKYV/EpqT2G/pEtmiUzw==","signatures":[{"sig":"MEQCIHjxEjWbU/OfYd5BmUyKOHwO5Tp02N0w6bep58FVFtv3AiA8UBWqlD7d4zU/mZIg2fRdQGDBIOgBeaw3mfE6PYRwKA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":115207,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcdyRTCRA9TVsSAnZWagAAzdcQAI1e3XQm1QrdQgmMMKl+\n/9WkMlIymB+2NhulcvbnhIg2aJ2zTxhU7fWplRINzb8zcgsc09ZEORNVM6Xw\nayrqVFR5ImejKB8DE0K3PiWg1XIZqxY9uk/avHSJaqZ2ORiJBC8qGDdFAK4R\nvHPhV0oGZFb0uKXi9xHCcbvQ8e6EEW9V99zHX6oAjv7koyfGK9x02FfXObC3\nEvqBppFC3Om88tlNowBF+dJZ5M+/EyM0ne1wyN2rgV1MHYNZtkv4bugTDOpZ\nuVWTDE69h0UNT8dLMX6VVTXxwpsIusfIcjoFsiXpQWX5Mb1Gz9PAUtcsa00P\nvHOrN4xRuelvsmhQpTfOWvDhAnuu9b3hVI9V2lmUShuGh4sRj/1VUJcLtZh9\n9wc3KncUXcZSgqg7qMQOJAHRJlVLqnhocSWmIL96HI+sNQ6CFS/zv3vt8uc4\njpFrt0/RtVtE2HOLltX11OT6aBWbHjrNDT8I+ZxKW0OgTCFiUaBPfJSib/8m\n0338da5LOVpsNNpa8BBQgOjpYJSXZ7E8Iavq97jC+3Kuz3BQDLvD1tGZWU21\n6cpYKOyERlmX1n7QxMiN87d6+h1eQbO/7t0kAHUwySzTiE+Tin0v67oY/2HZ\njF42CwHnxPmBsIUa/9pjXgDcbM3tonCdBBceatrMEO6+UBOIoIi5YyZ1nMd2\nsVwn\r\n=exsE\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","_npmUser":{"name":"acdvorak","email":"acdvorak@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"6.8.0","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.14.2","dependencies":{"tslib":"^1.9.3","@material/base":"^1.0.0-0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_1.0.0-0_1551311954738_0.4060536446934544","host":"s3://npm-registry-packages"}},"1.0.0-1":{"name":"@material/auto-init","version":"1.0.0-1","license":"MIT","_id":"@material/auto-init@1.0.0-1","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"405e2e101c8a0e877901f9c532fd210dbc792d28","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-1.0.0-1.tgz","fileCount":10,"integrity":"sha512-vzU0fiYKyWBJmkN94Kz9sRKzmeC8P7I3Fn7Kw2uHVKZMYDwU9xcSBz63C4LUG8pzut78+OXPm0BWX1SvHPbYHQ==","signatures":[{"sig":"MEUCIQDPghZNqx96JEfrbLiV0AvbN4BwrWv+2Mpmtzwi5dmd2gIgEBsVsquJNOanoRBoLKkIbVI4hiPGkPDEs3nFwjWCxuQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":115213,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcfbW1CRA9TVsSAnZWagAAXfEP/RA5etpN7jwnWBhTScSm\nnc3J3RYR/fewop7o2nK8XmrZAcnGlWNHz09sfI9vyPTYzYV2RwDUYhG2E4JY\nM5/Y4AESgB3EPh2swzREAGlCoy6yfk4PcmfyyY/j1NF3yQXsEVayH4+9RNIs\npjuoKDkhvsd7ZCc/J3j24uVFDEBq5VDn0gRbWj0SbCR1jG0ieZGpUptOgBU3\n6tFJLPz9bWIpQGtMbGSq8U5UQM+C5nEqE0I4TR3sp44+v8SDZcKz5t/pAUXh\nUeF4gfEGxazVaeXMv79WwPVVW14c0r02/MvCNa1tmBjm14FTBnwlvSvXYc4Z\nhAXMGGRdMIdtUHIHtdBUjDxJIHTkdaV8C4/SGp8cGbYcYx2g29HedkRNZjDa\nYDUnA/3w84nucULOeykxVeIAr6fxiqWxN9q5gyGRhmkODNH930wHG4HlpleK\nwTvEScpcIKSB0SsWndFFYL5G3wiuHv+/8CWHU6SMxs3D2dtn49tvZqhNEK9i\nEJJbqn/6l5/pFya72rOL3NHTH2c/c15aOC5iSEVfXpgqSL8MYSiB9Cr0UO8W\nd5ccWKe4E45y//5zQUZu6oc3JM0DsfH5zVpKgTPPiPKU0Eb57dxpzaojHfLK\ncprIYWW1xtM0FqfLmnCqTIq+o0SWgOBxxHobdvgEr/W1uqUQ2y3YVDhfUr+X\nsR1M\r\n=up7J\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","_npmUser":{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"6.7.0","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.9.0","dependencies":{"tslib":"^1.9.3","@material/base":"^1.0.0-1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_1.0.0-1_1551742388582_0.3743176921546749","host":"s3://npm-registry-packages"}},"1.0.0":{"name":"@material/auto-init","version":"1.0.0","license":"MIT","_id":"@material/auto-init@1.0.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"0431b03f1bd533f57c4532657e236fe47711f3ab","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-1.0.0.tgz","fileCount":10,"integrity":"sha512-xlWEjjyQquXMi9xz3RH7HW/5dsLGkVYQnm1WCYw2a6JIpIlipkkLEzBNc//agiQongIBbLndL07gO7WQeSohNA==","signatures":[{"sig":"MEUCIHiPqrLDy13D1r51MntnhHyiAriakRbB8+YUtifQ9Hn5AiEAw0jWyN7TdllMgm8dXbpaWuRTSbpZoJ10FJ7R/irTdPY=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":115209,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcgDaqCRA9TVsSAnZWagAA9bkQAIb03+4qwOfqkGPdmGKx\n2LIruwL6VDoOeKTYIHYpQHX4ZFhlwPCsadmEeiu7qqPxx4xtHiJJvwyIk6ei\n14jos3/s0sl2rUlwuEaSNrLjgStYcUXR3gjf/lMcB0N64bpP/fdBZBmGQuc/\nYs6vSUK9LTWEE2EQP7iBN+6x3no4IvVVAotdYQsTxDR8fdu22WJy6+R+SzrW\nSIjliLvClD8/kCO+3vVZV8o51HBCJlkLthTQU/P23Vy9B9dFAdVEBhi8g6j8\nI4OFi/9yWSvs3cqDTH8MECcGNKVrTfCdxPHatXTSjUQDk/FN6cU6DrsvGu6h\nNA9TgVuuFYNkLzjUoVHl8pI6aQK7Mb5rN5d5PU3F7yUL+wsUTftPuLWnaIH2\nxpG6k54gTZW7mEeC5xRgIb21cEDO72oqwjmfkUPc7+06LSUlLSxUMImOOjDX\nCm6d0ZjtDQZOtDKCa0y1leAMkB/weuMzSBPISrO2gVNOPBgceoMOXMBkPYBC\nUa2wHHUQksaEWrhWaN4ZA4sl/PeOOIANsx/VuRexMLSWV2c9FJYdE+UcxE19\nI+TGkOuV8Z8LegZ9/J/fSYuulOTm5oyISX4M/QA8+egPJYNSqbLfFX23dZ9q\nmUaN9qcK1r9Hl4huOkCJ3WH7iHvgtDlcVBAl7CLJfudzfqA19WKhpSInQfSa\n/tyX\r\n=EsaU\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","_npmUser":{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"6.7.0","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.9.0","dependencies":{"tslib":"^1.9.3","@material/base":"^1.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/auto-init_1.0.0_1551906474041_0.5243641112913822","host":"s3://npm-registry-packages"}},"2.3.0":{"name":"@material/auto-init","version":"2.3.0","license":"MIT","_id":"@material/auto-init@2.3.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"3d32507675939ab0d7c9f05b075805ed24d22095","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-2.3.0.tgz","fileCount":13,"integrity":"sha512-WFlX3xdZjp/gWZiY0+poFjO12fl8t8C9M82kkQLb6WaUkoQ1YHeV2xQSDLY4IvwcKXb70IpcU3Tqgh+aoiHC0w==","signatures":[{"sig":"MEQCIB6/ou3HKer6EMbaTENn4oh1x1mqY1MImzGYt6R+RwzBAiAN5DRiBUttl5I1PCvk0S5l3vm7qyEvWzVs/7g0PmXTNw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":79053,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJc7abXCRA9TVsSAnZWagAAmkYP/2ALUPhR73ElXeGhXakD\nMg13k5MnMiSwkeFZhvg4Wl0BQAh1PE8O1D8MsP4NebIq7ZlQat7oiVuFpTZH\nYZcUDab6wZII5jmFZ+5LOkTAysaJw87+vnlTksjsW2WYjnas9eQGxyQkeqj4\nrBMaDO0ssKZHtoqxZS+/LWNsy2xQRc1V/g7QPUiWCogbrkHQ8dptGUM6gzmO\nzmHcwnWL/Xn/gW4otzLYrPY0i5u3arevmlYSrg+2p7yW0DbO/UH2ai1WE1s7\ncMjN9FqFORuyGlkqX601lhhk3Gp4E34xQ+TACbrlybEh24jvp5LyTR4PYPFA\njDyoQ6K0zRFxT9CXvHP0dhp90Tqv4QEcpUfLWMd6O7sLMmEPrrREAJLLy7PW\n7qlnKkujBmtYWqf5nlL1iY2tHkfjkJNStyUVEYvC8wLTgO9rMalqaz7h7MOw\n/oU2PF+NNLcZG09HnWibSSsCWr/tvS2giaqLMGtOX43tw8Mfs2Fpm0AdN6Sk\nJ5DEetu503MqG6hHYCltfGEBj2LoAnkuBjkt2x3cArnIlwDQDqcIVOTroG+B\n3ev9GP75K72/Aeg4+XcGcXi4EiZh/ig/T6wpzEZP6wzR6Jf5nA03yRknQqGM\nVmqyTp1d4jgd5us1/pSeq68pArht46BrrkakBtDVuGLFaTz1Zi9mPXBe7HnT\nwSb9\r\n=l/X+\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","_npmUser":{"name":"moog16","email":"mattgoo@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"6.8.0","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.13.0","dependencies":{"tslib":"^1.9.3","@material/base":"^1.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/auto-init_2.3.0_1559078614760_0.48675643857628903","host":"s3://npm-registry-packages"}},"3.0.0-alpha.0":{"name":"@material/auto-init","version":"3.0.0-alpha.0","license":"MIT","_id":"@material/auto-init@3.0.0-alpha.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"492374fc1e94ce53fdc1812671f1977d5df23d9f","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-3.0.0-alpha.0.tgz","fileCount":14,"integrity":"sha512-oNbf4sBdd/hNQMOpqjteFqCJH72iebI+0dfZYp2hVX2gWXWn30WoUk538KyqOjblGQhFpdf13he3crcaZEstbA==","signatures":[{"sig":"MEUCIQC8QqNqXyfSvNFOy2vYmyv5h5dF6pzyoi4KajXBcGo65gIgSVEi2yzqVPDKpEI/bSD5WUzeMFTznhiHTWXKZE0wkYI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":80196,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdAHpJCRA9TVsSAnZWagAAWBQQAKKmVx905xrrVT1ga7JN\nK5Rzrctu7miNhbkc+YXk3iD7ySgHPHLiL78J2mq487ArqWxa6JsDWNKou09h\nq/WwoU4VpRQ0IdMsIRkVXaZXeGqe0SGqaamhk6uK6kJy2mGH4DaC7ZYeu0q/\nH+P1vG4fG9zrXl7QXTF3mw4mgkm/tfGXAt4z8igolzXGSgFoXsUA+93oAHBo\nbGHxayHyZ9B0CdRWKNaZdgav+fbuBnD9ErehyuoMjqNd/R4UBnKspwqYfPyd\nRmz0C1OHhBIPzaHu9vk/Y8nWkjKYuNT4ewhCgT8oxsTMbBzJ6QAnkGbwZpY1\nWLQ5AjL44v6bcbGKk2BAWGQpTyLtG9fx7rk7pcTk+m65UkG14YXeXW/xzou2\n8buWjTuYn62MXPsXUEPwNe5GDm608uE+leK579pKW49Wx2TuJxscj4y9I9nl\nNnElvdT/axyJTeSq/EuG6aGYI8/UfVcbv8Lxudffltgede9mgZM2/kSFrjRw\niXUDj/MQTruW9isrkkt5ONK1Zq8JrXxR1AU3/DuYtaaBkG/m0RCE3U4N8l6m\ni4ou4Ng4/hVbWB/mJFItXPCCwbQaLe7CdX/k9hU3jFraFO5wnJp9XvrHnJvk\nhkJHFkcUwpvcv8OVM3MdSRfog8weVSkAeP8jBESyPgg/utyxEkqRrsgHu+sf\n56ey\r\n=tlZO\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"094e507fcfb488303e5adec97f7f985b30e8567e","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"lerna/3.14.1/node@v11.9.0+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"11.9.0","dependencies":{"tslib":"^1.9.3","@material/base":"^1.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_3.0.0-alpha.0_1560312393190_0.987722464224531","host":"s3://npm-registry-packages"}},"3.0.0-alpha.1":{"name":"@material/auto-init","version":"3.0.0-alpha.1","license":"MIT","_id":"@material/auto-init@3.0.0-alpha.1","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"da83880ede602d245c4fa79f01bf406e037232fb","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-3.0.0-alpha.1.tgz","fileCount":14,"integrity":"sha512-glHtSOPSptTzFK3GqCYwV2hoCu1KQnHYBIh0Aq396xTgoYL5Mhfx/t/6fjp1lWf85/XDqaaf+iWze1XdZZKGOA==","signatures":[{"sig":"MEQCIGr3PrRD1Nav8CsMQwgNVnTHj0DhwsCkq7zdJ0z2WT2/AiACyF7gFV3R+B43UypG2ruC40mDqcqG7IhpOkaO7rqmtQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":80196,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdAUwlCRA9TVsSAnZWagAAgJgP/3m+4H+uTYQrClXf350q\nTpzEFUU99J84ghOtr7EJbFQwwkIKTBVRlThb+tfuijzYJH6sVbLCLn/C0MBJ\nz4hD8HTPWs5NffIqmU4qGZDCMo7qVBo1pcHSVONK8tzzEjD+G3ynCut/x4As\nkobb42YWKfRTMMPh9JhJNWbhIrtFj3Nw1eD2YNURlgn7nLh/qu2yQkcaB1q1\nOle4rt9Sev/UyfXY4HI0lmZmNetrcyC8mCEb0K9Qp7VafkM68L4WsLaxnIgH\npcS4gVX38oenOUXsE2GDqq8Q8qFzjAvtzGdYJbfzCB8bpxDVlzzDoFCA+kKq\nufM9T5zDstM6Jq+oq5g05VB3XEzG3ndtzq46CdnOlBBicP3+LyYASy/duCTN\n4QJB50U1rNck1w0ibhLTEtdzog0oCKSw57hDu+kpKe0r2xK9oCT0q9Aekyre\n4u9riFzf7vmOCwOSY9nRcIUplpAv5gq2KPyl+lxG9cDA7d0y6et+F3HrXbuW\n7xPwg4qHOKFu9U8R35crT5zEaprfg4QbfE11nSmuVWaeEC6UUd2FrHqz3N5s\nVsGbzIylfvEWGPAwSLAgjOt/FBP8yhlY3UoOrUqGzuSPIqrrYJrGUTK30SeR\nEAXSw+o75doKsst9ZGpTun3Nm9MLDlTXOj3XQ12kTiEFmVuLmAtGuhwJ2MFQ\nx6K6\r\n=pMza\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"dae97b98c21bb93075a9688cf1f9076a4fe5a85d","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"lerna/3.14.1/node@v11.9.0+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"11.9.0","dependencies":{"tslib":"^1.9.3","@material/base":"^1.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_3.0.0-alpha.1_1560366117127_0.5371070188716947","host":"s3://npm-registry-packages"}},"3.0.0":{"name":"@material/auto-init","version":"3.0.0","license":"MIT","_id":"@material/auto-init@3.0.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"2047a717761d9c2aec73174c98ef5f6fb6f59d9e","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-3.0.0.tgz","fileCount":15,"integrity":"sha512-svfoUupWj0oZkPbviLifhfcRWdFDuHmOYdJz5p3nXQteTCZxSQILw6hu5y8IoV9YEwD+QosHu5elpgM6kfE8wA==","signatures":[{"sig":"MEYCIQC06ZbcAUy83PsnLn1oSccUxmfk8e22788imofjR4ZIegIhAN1blDqdXhW8Nqyi/+JGzWlp7Y1qMHcarTrruk+AYaQ2","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":80527,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdEp/kCRA9TVsSAnZWagAAMYcP+gMDUDisuvbfOIk05T02\nd+3yHj+ZJJm+urSuYZcmCr5q5NxjSQyAobn/wq7mZdfOJLVtObjmD5/h105d\nKmyjSXl9pR5kTwPqZ+QQOXR6nd+afrhsdjYDXhPWen6ghZwMSQook3+BdGKC\n56s+XFTan7nHEQV7IpJ+3X1WDZD+gDj98BY8bdAQvlUghSrLhCJejl3BgIW9\nUuCM6P/MA0/lmb+RWbAmV6ubo39SGGbYvaE8X/r9KncPLlDunQSG2tI0/8wZ\noeeqYN2o4VMWIy3+P7wfecwNiGmcZjQApyjyvgTCyW6VNOnVSZrTun2tRXd+\nmH7O7eHXajTfjRaPWMtdXYg9qPQx5zrzevtzc9vsKZfIS3DAOycOhE4X+Q7e\n84Us2CTHviDOAka3A9Xc3ELtvvAGCR1g9oL/qMdbOalPoF+OVU6P6VTiY57K\nvgyZ3OybZuOw4cyV8uWDr27z/tv+7EBldgayLIwAc+CAEjkfNHGnQ1hISDCo\nHC8UIq+4hM9ae3uo1JqcwzaOO6vJtDcTvUsIRX/O7JP1xO1lJV/R/zHnsreL\ngaGwLL8897YujZ3lM7go8YWGo6R8133koob9S8mvaLAY8GOdgNBqJRjboSpB\nA+Qn0PimRkYSi1/7RAVNQe7KjdRo5y3jOYvEdeWRCSmu3s9SFbwUzOgZKpDI\nlEnd\r\n=Ietj\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","gitHead":"747f6ed544e3a3bb3fde71ceaa51359f2212bfb9","_npmUser":{"name":"moog16","email":"mattgoo@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git"},"_npmVersion":"lerna/3.14.1/node@v10.13.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.13.0","dependencies":{"tslib":"^1.9.3","@material/base":"^3.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/auto-init_3.0.0_1561501667573_0.6407403545354113","host":"s3://npm-registry-packages"}},"3.1.0":{"name":"@material/auto-init","version":"3.1.0","license":"MIT","_id":"@material/auto-init@3.1.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"bf2b1dcc12d9c09b1f6182f0ac0dba7c0986883c","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-3.1.0.tgz","fileCount":14,"integrity":"sha512-Q0fuycL7JUyody+V9h8Y3mXlchNECOwCWOWwjJutcxeIqmhVJxf5qiJJnXZYrwQMMtUuO2A2DTHdrxCITL2COA==","signatures":[{"sig":"MEUCIQCPU+ofspgiTY/izVkX792CR6dKZSjoDJ8EjBzHgjzyRwIgdO9FhrU+52VeFw3YjmZ9I1tENMslVPhNJsbHSb5VB68=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50363,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdNjJuCRA9TVsSAnZWagAAtWIP/0lalhmg4i++/6PkrA6E\nDXuADM7az2uYYv8Jouyr7DPvkSQzDr7wc1jbMmd3q8Fam8eQey+rBcsddmh8\n/S4ecvu4tDHHwgE7CFQ0daOuz9G91UGgPOyv6Nm3SxoVz/2mEEjffcbKFX3/\nm8QJ1FYYy0Y5d+jLOyaJ3QrpKFt1o9vNVoejgygeEcT/Oy429gL962k6R+Zp\nV9tvku5VlFByfzLugxgFe56qBTgsxpAqC01ISN5RvAAg4u1DKLd7o9RjZGZc\n9AIiDCojQFECxJRe/jZ18JbHqKgCvl0PxLs8vYtIjyZrTb6EUUYkHxQH+C82\nC8s9kf1BHcFrLR7tFOx1tbkPHnpjzoVNFk72JCynaKuOa0DthBZoCr+LSkjV\n+FAeclTUQCqLF/FQ08DvvXhiJGSXQUKUka33PlZn5Pse7coKaxxIQmrBvcGZ\nNmPFln8G7wboPq7YMnU3lGDQjEZ/MPhOP4kCsgESSwIZ2zrA0UAaf/tTFrwZ\n+BLgmTCaXq1HRfsT5DnBExf7sHLgECE11snW8d7IDFqjAEMdUY+gl/jgewqz\n/H3gv3O4Eo7r8I8yYWvD9FXEc9q6n54qcZ1XrGvhepw9dl34aBcapqC1cCwr\nrOAp9oc2BiEcGiSC0Es9REMGh6Nb2n1y2X5ipMAtSwJfEZlZKXU2fzgN+qNK\nCLRr\r\n=G/aI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","gitHead":"6b7e616da1a1ca53df2253f6207642739e13b5dc","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v8.16.0+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"8.16.0","dependencies":{"tslib":"^1.9.3","@material/base":"^3.1.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/auto-init_3.1.0_1563832941213_0.33678386044200903","host":"s3://npm-registry-packages"}},"4.0.0-alpha.0":{"name":"@material/auto-init","version":"4.0.0-alpha.0","license":"MIT","_id":"@material/auto-init@4.0.0-alpha.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"lynnjepsen+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"3cb209ff6204450424bff58f271008fa72d79a28","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-alpha.0.tgz","fileCount":14,"integrity":"sha512-U/0PLsuR0lA8R229kGzrfBu9NHKVA/+aYJL+ykrsqcVcTv+8ZLuvpLS7PPy7/DPPDRVN4NnIn2TrkdROaITI1w==","signatures":[{"sig":"MEUCIQCQZDEDvW/K2DbJZt7p7uJaGfmotBa08HGDTWcGJv8QPAIgGYalWqhJDyqiYU0KF9s7xGKhmknZI1vjUlltZwGylf4=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50572,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdSz34CRA9TVsSAnZWagAAzigQAIen/Xi3akXS91yXN/fB\nkK3VoofJPvW2NMz7lgtPW2vEz8oZPYMXjlAygyNK9yoj+PIarFFyfxc8GNgA\nxaHQ1Aza1cDyTwd6n12yKQsGFN+U3K/eYI+ezCkPL4uMpfJ0L7BA8G13vxXQ\n1tF0W/K91URkcIrXG+CmSvzMiNTM+8cwqiAVxwmob3ehDn/P6hXhJi3v9VEs\n+C1mljFg0IP4kyH4LIOt1AJqUWr8DqhJynrvPnJcXNFcLIxNk+5mo1jPpUVA\n1DpRndzbTYBOLnJfYFz8wHilhY/Bm1/b1XOwwcKNBmEbZAjTmIelXw7ylXyN\nnRcexNXUpi2kpfLaErOJ7b9r52wrE6Xd6eyoP2vgfvYymzdCljwwoDTRcIku\nPz68GqVBfzcluC2Zklr2S3EpngMv0CVtOzU4G4bSMSaWnfL4yqhlidlxX/0N\nruODbpQ5gS43njSyDby61Rh700o3Phl6BhPj/VFtKAA9xlSSjvpneTzIqitw\n0RToxJCMY1rWJIaR0AZhNQIuQP/uDTnqXYilkZxzvhJMPDtKEEW2MqvqzY5Q\nl42cqMlG7Kx2okXlfpEVaPjgHRlWDwSfP9IZUbJE0YZJ8G4OTokH232qXZej\nSfYDxj5mivvjcg05wKma+xICkCUaDCUaRTbjXQpQ+npXPwA55vUU2r8nUUCj\n/jI5\r\n=E8Ym\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"184b37f65b79a260f2835bd44e422dab2402d937","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v8.16.0+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"8.16.0","dependencies":{"tslib":"^1.9.3","@material/base":"^4.0.0-alpha.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-alpha.0_1565212151689_0.7802508294884802","host":"s3://npm-registry-packages"}},"4.0.0-canary.0":{"name":"@material/auto-init","version":"4.0.0-canary.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"82664ebff2910e5b68427fe96eb4175bfaafb587","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.0.tgz","fileCount":14,"integrity":"sha512-mVCAYPDOvaDtiO0Wuxdo3dYi8Z3TiF2AYuYhPcb5tWJLO3pqpNkkJg0q+vkIpMRZoWhgh5s3ZO3nncDbq2WQSg==","signatures":[{"sig":"MEUCIQDeOBRhNiR6cbMgUbYZw3rCCovZ/mb3bv8rGGsT9ARQLwIgECcEdGpy2s5hyreZKenRd4JKTf8L8ygxasHL3/REao4=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":51559,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcJERCRA9TVsSAnZWagAAylcQAIhqRKHJWhnPT0WiZsM5\ncuB3k68F6YHSQ/it+SFR9fnTd7+zMw7GBHRMHA/HlAmvUJZPQJPIM4dmz95X\nvWd0hhUlanCK6D8zRyk2kOQkU83fQAgQ/4etIcsZTFDyGltvmv5xoCwklORL\nAukz3IA+soNtG+jq4rh5/tIMLAHhHrV9SmKySYUTzyu3tf01TwGobn0O+xnf\ngsHfRA4uBjnYDO1WAVbvbs/FJf82Alcx8bBp0YfRPGMVXXTIGJg1Vq1k2xq0\nQkWUOWYdX3y3/lkzGexHRNciy6ah6taoE0Cdkx3mgvTzHgD4MsOhvs0FL0y0\nOLauALmhNk0QM/UQu1+hY3T4qBJMXjt1u6/lYYOYpxKUuGJMLo+tV/J7LivX\ny2KwO6SskYhJnbBr1a6v1/RURrbiPe4w06bEB63fcG1GYdXogDjW2zAThqYW\nJZGkknktrtaRvEal7/cqwFnmLb2l9yN8b0BI6s1QVO/jMEeL2C1gQPyrGZP/\ntFPNjr5fgBITleSfYsxzpPzFT5cPTSd2YQpLSWn2c1xpRRtnxUkjAH3J+Buw\nnlfxn/lSEQ5EhKT/8Fw6Ng3XMW0HjgMEwjP0WqSDYqStwibhIUVR/bENWKo9\nfe7lFAZZvDs3anaV+7Y0RtzsuZXSrC3KPhSJBtGHvjoCzvgz9y0ljuAIGz9p\nhgsM\r\n=AO/A\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"a9e69493144f4246efe28a958126afc2fedebd60","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v8.16.0+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"8.16.0","dependencies":{"tslib":"^1.9.3","@material/base":"^4.0.0-canary.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.0_1567658256838_0.4804646030152564","host":"s3://npm-registry-packages"}},"4.0.0-canary.1":{"name":"@material/auto-init","version":"4.0.0-canary.1","license":"MIT","_id":"@material/auto-init@4.0.0-canary.1","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"9ccf30875b08856bd0a1415c4dd88779f5952bdc","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.1.tgz","fileCount":14,"integrity":"sha512-H/NXdJgmOdxY3BvmKcAoQxlhiNmQ6OhruLRwsoyKHBYqKHZQk3XbxQa+wsVrmVoA9c9PH4wRtZriH7vPKvTzPQ==","signatures":[{"sig":"MEQCICGYJrXHxYrSai7oslH2vjVJrmvQOIMcKGRiGQikTXFYAiAb1W89t459jLBrWL78i4vCG+um6gIJOqiVOE2N/5MMHQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":51949,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJddrQSCRA9TVsSAnZWagAA/M8P/2a7Cr/akc0tu69jjGCp\ng1rYP4y6m6kDG9eXy8PMfEAyR4z5o50fVodF39iz8hlrRgGO/OfWn1d2RUcb\n4oho8fgdjZuIBT7DtkEKJLVy9hSiv38ezVlCWhV4x9F7+t5rgob2FGefHyEz\nADEnpKvF5gSOZJ/bGsYP4zcI5C+N4Gf8008OvSlXqMvz6EMMhSympsTo9NHc\ne/3zIoktX1yFCxojWacnXwgxginNjdcNoKZYHLIFt2evULG0vmkWYIaB6xmf\ncJOxNCDloMs3NSFjJFhR1G0D2umT2ltDtazaWLf0l+B9UAgF04KhnU+DUSpU\nO8+U7f9vkPj28IC6izVphVtiJNH2wwq1IoBO72zwVNt/2a7INJfkwz70JMIj\nCZWD+HmuHh+dvXVMVKotecmYyHPt8MAyr3TZXVyB3BXSYr9HjoiMs9dEmVjr\n0NK6oJEzrw9c946mN1NvkKFBvYkC6ZCHexRJ1idqafaAcQ3FBUOgSLfULqI2\npCPa0LF+89FQj0gPKvu/k74FOFeGK468PtDRusShmFufJOOHCIvs0P4S8AKH\nglkhoHv3Sfa6Qw0xhq/Mh6vNorrcSVpRYwuooM0m2jQ/T3QV+1Jp1CllAnsL\nDHXtLnj8ZTUs7zu/8XJcvE0WYTQWRlec1HzL6+S2F63zRdbZClhTEkcuxHvH\nvKR+\r\n=QcEt\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"edc72a4d7d6a61d61620fd05a80e2491e518bccf","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v8.16.0+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"8.16.0","dependencies":{"tslib":"^1.9.3","@material/base":"^4.0.0-canary.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.1_1568060433788_0.22483855769873928","host":"s3://npm-registry-packages"}},"4.0.0-canary.79d881baf.0":{"name":"@material/auto-init","version":"4.0.0-canary.79d881baf.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.79d881baf.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"8ca147741714ebdfd2e87b1b21327675c71de902","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.79d881baf.0.tgz","fileCount":14,"integrity":"sha512-ZUGZHq5ij9LD1+JFEyViy1g30p1E6NlzSc0htYrDqamLDHBUgjkrzZBUcTnA1q0wCMWy+bzYsF/wjCzUx+hBew==","signatures":[{"sig":"MEYCIQC+6DD7q0MFg5Y4gIFbZnvvIIyeEeTUJmsbAmyqJELQOQIhANJAWgk1Ipt0/nwUu9YzKjP2jYxb7RpArpixS1Zszeru","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":53245,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdev0fCRA9TVsSAnZWagAA+VAP/i4uEk9yKjpIxLGjsyPQ\nrSqY9LUcBELD0c+HUywmGFFt6NaYNKiqxNzIVE1Grb/VJ4DufJjQeJivnsNQ\nLJpEz7C7jRAOhAIRN3D7h7XxG3bzOJJ4DRv9pjnoBUHy2yz41ymFg8IQj/CR\n9dOsDgtPLJYxzq/1JecJNibBoBxd7BrH9++YIUl2tza6g7y8+N1Kc698ZkGI\n/Hd3xyYIQ34GNbRtNGXA68SXN94sEEK72UD7d5emEmmOa203R4o/JVrQ+j/R\n9fQqxgOqfVJMOmdbRZHDdLokl9hcL7aTU4Ymp7uiyPVHekL47NR/fp7CD+6I\noQdJR/ifLuqZDSZ1cupPrUNwcV7EL+I0K0YrkjRECLXQxY4jNiAq4dDpVlGU\ntLHwBY717KR8XUCi0Qz8KxNRN/32pitf8MkqCaQVcKdkUoPwQ5elE8E9SBrE\nRAJjA02KXaZiKm2KommPSTxP5TF7awZvCZDPCNEFDtkPLFKM2ImcnAQxhLUt\ncEL7WtNmfDU55S8/Lzh9ZSLq95yg2qykaduOuKNyeboCeewPLZWOBsOVWyo7\ni6Lm10S/MY5rdbYymPfsvk6P6QdF2GpJnZdKd6Saj/j26yVY/bYovs5mCIVj\nmVJEwtO2FRLdH37jL0BVWqLuuCHeqUcXx9hr5sYdzp+k624gwIuEI+TFBp56\nZzrY\r\n=jITz\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"756806a2389389441b5b3c130de02948130d96b9","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v12.10.0+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"12.10.0","dependencies":{"tslib":"^1.9.3","@material/base":"^4.0.0-canary.79d881baf.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.79d881baf.0_1568341278590_0.17935975021886197","host":"s3://npm-registry-packages"}},"4.0.0-canary.e851d4f40.0":{"name":"@material/auto-init","version":"4.0.0-canary.e851d4f40.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.e851d4f40.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"b2ad33c8f643f192001d84bccce8cc12ae906055","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.e851d4f40.0.tgz","fileCount":14,"integrity":"sha512-zupNS1FsaRavOiGH7I4qWQBpqC+G8mbglWoyfMQFbvBpWwTYi6O1uC/w/SZSYFtLMfxv3RZYsr/BFsNUUxE3Mw==","signatures":[{"sig":"MEUCIQC8U01PxFGgy8Q4Ddirhpq4MN75ZCf7bsxNBCzXl/BINQIgLMV3O6+jq1OOOb23mWIG5Bp2CoIUN/ZOGob7MeVVQv4=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":54965,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdexXlCRA9TVsSAnZWagAAh+AQAILpJiZ+WQdGuL2A3kCs\n3VP+20vc+ZurmD8OjbUnX9ctQwBHYnnfCb2yGklnHx36fQCqG3E3fZadS/x9\nZ4EPdLDvoSOgz+m5xM9fV/Hhbp/lNBU3OEK+L8A9bW9tdI+GAqsPkoF50g5q\nPDKl0VOY42BvERwfLl1NH9+zcr/Hcq2ONJEBu8TThd5Qf8h+KL7EzV2xigfW\noPjEQkF+fCaBdOSZ+aiNP2H48d3dX4kSCSu1kC9wIhUyks9cRSKtCbkwGUv3\naYvCT4NUj8wCfpLdUa0U8Henmy6traaQXNwjcoMEDs6lKfdzYmUzzCv2Lllq\nPR8KVyyIz9qw63DpVMrYDdIpdBSnLTxYPR5ElxcGeamnJ4tE21uTJnhCkx01\n0GSGc71uBi1YFDVnWCnOkZC9mI22+qEeIFTuW0+kjVRN0/dyn5FOhoRuzIcg\nCGwhBA6PjjIyTrsuKRj3LFDwrBBHpMGijlo9CC6TjyO7jY3O39ufhEzQNmE8\nlY/OlBKaCBbvw3yETe+jLdeQRQTchwECV/pVU/H4du8IQjT6FzO7Ts6dQfzY\nveZPyXixg+twIcrd7KYRgiVNUnLLdqU4zZvecbB1s+gqMx8Eh7sQqx7ovNEe\nWxqCNfIvxxXlsG9dJAnfymbHFR+cQb4cIsB2AsEoEjytIcoLxoF5Ve6/9hB5\n3d7s\r\n=Cevd\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"353401bd143fdc2b4a85abf330176228e21dfe13","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v12.10.0+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"12.10.0","dependencies":{"tslib":"^1.9.3","@material/base":"^4.0.0-canary.e851d4f40.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.e851d4f40.0_1568347620671_0.40826598308398365","host":"s3://npm-registry-packages"}},"4.0.0-canary.905884690.0":{"name":"@material/auto-init","version":"4.0.0-canary.905884690.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.905884690.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"77599eade03ca4aa09fa5ff03e9859a3612bfe7e","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.905884690.0.tgz","fileCount":14,"integrity":"sha512-aKoemxaRdQsvYVxsIqWoy7d/UsOx8AIpFmZJadIIqkIrtVLqjitUN3bk9ApGrpPt+RlZBiymKqAGJjGOspMJxw==","signatures":[{"sig":"MEYCIQCDnACrOV/Mtusw/v3DxpHYQQP/2wzLv8WSYP3olbXJFAIhAL3mZ81ajYbP+NstM20gDaWlSM9siWLXo6lzrmZwYv3M","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":55180,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdgB8wCRA9TVsSAnZWagAA/GEQAJn+YXqBHrWY9pGNlKD+\nQ+/awC5V4Zf6bcOpF77nNtd8XnBxoKeYgvDhODAxWTw2ymQrktvwq9Ig7fqs\nlMKZmiyrrAvbLLyk+SsjyzYyNCEPrpz5yrqB6Im1UoNPghsfkKmNPsw0S0h8\nzB3G4i+LExEaDPbLY2hAW+/HmvDTI0fhe7aehYgGloyCyv1I/Uul84DnvZf1\nX69mV20Q/xB+bqLI5jmT5D7hwgSQ6UF4DL+XG5GVU2xv91fkld6oi4/6fm3x\nBD7KHq6mtVkQ0P0y38NlzYOUXNKSdK8ku8ys3xO6VECMv6xj1600sLBWxYLE\nrP3ZcWi3UO4bVxLcl36Q9PzAulvgI9f+0T5+U/JhS4u23z7/i4AoY+3Cdn8H\nRE7jittdRv0xb5nViKZNkiOk9NtADKPPxnWRiGpHHDETpoMsKeqgyB+e3Z+q\nq2W3YD85hIf1+AP5wTrN48kZTVq07/80zR5MZF+CtCDd2miWwbrm7ibU9S6P\nqpJiF0vNFsMqNNbzIkVW2ZHh5KjL7duZ8V1Zdw0AvtfOHZqrIn3AMcsiyvie\n/cHXlkQrm780YBHqQRnSUP3Z5Aj2jZ7e6yruI+Tkjsqg+HIqKcStnJoxKKHE\nZW1jaVlbFWgBuBmDLvPnIXn21PUDIfCQGUhSxSdkKUqdHIHnnEuE/So2vbuL\nkOon\r\n=Kqxr\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"df7fbf65943b1227b1bf145a2774abe7710b1e30","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.16.3+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.16.3","dependencies":{"tslib":"^1.9.3","@material/base":"^4.0.0-canary.905884690.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.905884690.0_1568677680221_0.0994982791052863","host":"s3://npm-registry-packages"}},"4.0.0-canary.199534d61.0":{"name":"@material/auto-init","version":"4.0.0-canary.199534d61.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.199534d61.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"528277437bce47e871c1526e8ab7e3cb6b0b00bb","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.199534d61.0.tgz","fileCount":14,"integrity":"sha512-N/gUye0IMF9p9Mo4sItbJ0ZxBLqFEDSS4f2EplsG61l4EIsVjIYMiVpoF7dFoeKqJZPxwiTaguZVMcclpjCUbQ==","signatures":[{"sig":"MEQCIHhEu8J5kyOSlZ8GzaXifO55IM2CgWv7HUB6SCmddPbZAiAWH/SBO5IDKTRgtCfzWb2QWf1Or6cDHLAXiq0Fm3JGQw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":55395,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdjlubCRA9TVsSAnZWagAAYLAQAIToK8yLj3TclICv1sh7\n4qAGSpKSJ5bZglbl5YchYh26OTX0RafmhNJIILgA2/t52uUPv1LTmJxg4tGt\nadDVIRMDsUIpYGazRJRgamUFyvVzHO607nRLaoTg6bnVrQniOivkK9IbkX1m\nPIjU6VTHmNr9MAV6QLo6O+UlP9WmeKK9ST7TGLgNGV1xkUng/7OJJkkaXkfd\nLxbrsNt+V66sz58pBzuaMRTiQfsVOyn8AchxENN3WGGWChMSd55NpaoUi7p2\nKIhHDs0MeBFyZQGjvGaXtapHN7aRTOUGVwEuZ/Cse+FTVekI09PV5I9FIqZ6\nprt9hIX5GxhHTC5ZWcBu8x8f9rrMWE5bgNckPGSXa2q+o9JIBluUuff96EQU\nO+FR62fR2/9Sj6ysMvpHhhTEVmlsuYoCdk4rBCIpCNnyvGCIaMMPmPFCuX42\n/MVvfVKFSj/q6avCoFfGcGlMA5npnM48RBB9nOLF4yYCmEnij/4u1nEwXhLI\nJgxFiH60syWpt+C1kC2PL5Hnl5gKON1fZH4QC4Z95zcJTYVdLgwxrJ1Dnke8\nz7VTaU8+Y9HbRaQvvmS0OqcAv+hZQ2oOi0h60t5imrXZYjFrzGzX0qVoEpT+\nEMfpf7ONtBFpeZR2u2P/iaSfTIoyhtRxIab7MB+VOA0dYLQIE94DNq35T8aY\nWtHX\r\n=Jp5H\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"c35810420b70c99e38a1438e1fd44e4bb84e21be","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.16.3+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.16.3","dependencies":{"tslib":"^1.9.3","@material/base":"^4.0.0-canary.199534d61.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.199534d61.0_1569610650690_0.964059960146407","host":"s3://npm-registry-packages"}},"4.0.0-canary.22d7ad2fb.0":{"name":"@material/auto-init","version":"4.0.0-canary.22d7ad2fb.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.22d7ad2fb.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"c2c16e1c37595317a9e258b1e5e54c75b825419c","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.22d7ad2fb.0.tgz","fileCount":14,"integrity":"sha512-eDpFkczvLZQZ06Iv4fxBqfiIn3l5aH9gNDrxCusQt1dZKsSpKX6usvqJSxumvE0HFiGp2+KUyA/WqjzzOJu7Fg==","signatures":[{"sig":"MEQCICPPPasRuPmAWtxmxQjA2PhGoi68gQ6GDgl1AmOz6kKOAiAI+rzqg9dtmmMdpWdmogmBYPxKX4J07PziEd/TiEwfRQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":55610,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdphZ+CRA9TVsSAnZWagAAcJsP/3EHQh5h0+Exd+Bjywwa\nwr2UkhypZmGBPwVjymOhVTr4h7cWrFjYpRDiyw9+15adJ5tO0ljuub1Klji6\noQU4ZChnkmMej8UDlMM2oD2jSOtflp2EA2MJthPflzETJ12hSaOVwt0gDIIq\n2JeQHLoD0LTvQ9F3fkPnX9yure4bL8NiDQZxGFkDzXN/veqdr+j7svRQ9giZ\nO9JR/OauEsimHHItjklleI5yCKqN+aE83oDFO1ZO5rDrdLB0s5rXO+PeQ9hB\nECwkMDSHZ6+k4Tlxi6RO+5QnilNofOzOEDH28HVWhIjxFJ5vHhYpLVDLbjRo\nwtwkqek/0pJIKBNPPSiUPw2FadxG1KJRXCoGo3bhBJZYfqbozzddquBug9K9\nKr7bM8VpwIoVOWtrt7ek8uYwCDS26xilmGNjlk1jyY+eK2iNTZhTViJ2aS0n\nGBsrGp8diZK7uKm+IHVh5ed4j9WTf5CbHuuXE8LDuwug95bLcvEtIEtn7wDC\n6kRdhYLwJ9KBq1p42M2JaFnz3ItrwZNfUOIaDkA2AtyHpe+fdWI4gZ2TCh5G\nWfBq07Czfqs2Zg3HrMCTKJC+lm0sPqQsGtU9qA2PgP6neH3m+3v+XGn9+h36\noKnF6QixOtmjaa/dnK+HfLQaXhxmjQv+4IsctnCzQFFjMCPMd1jFnYhq8aKQ\nE53J\r\n=QkBK\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"bdc05bd56f8cbc11face1f0f2787fdb17f450fe3","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.16.3+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.16.3","dependencies":{"tslib":"^1.9.3","@material/base":"^4.0.0-canary.22d7ad2fb.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.22d7ad2fb.0_1571165821306_0.2682683311790828","host":"s3://npm-registry-packages"}},"4.0.0-canary.735147131.0":{"name":"@material/auto-init","version":"4.0.0-canary.735147131.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.735147131.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"972bc85b19067acf4a0cb0e4038a0a0ce98a6c6d","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.735147131.0.tgz","fileCount":14,"integrity":"sha512-/MEhWqFLnZ0tcvtJIIV1KXv9AhGSGgsBWAG7z6e5iNRvkr2EKCSga+mI4iUY8ZQtvFRp8ibTauiF+ZyjG0/U6g==","signatures":[{"sig":"MEYCIQDwNVQnQexr5sr6E+NYI8p8cHhVSfXE3TmKMNAJ9g4McAIhAJT6paGhbYUBoSSl2064Pe/5baaV41T07xtpeRlu4clN","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56039,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdpnEMCRA9TVsSAnZWagAAGSwP/0xLUWytpzvHvDaf9PgD\nlukrzNQT/9MeFOiadiI032aI7s1ubqzQnVkEqdXa+/wBMdOwiXBBoJrVECgV\nJgSfXYwGP2mJuImk5tMDdTUbwsyGSgRg4ncos9k7ds4lBltGFX/kowXVfNcG\nnAF1JVprxk5mS5OlSpGZeSpPVgLeRPSRXD0L+U9LJSj3FKuQpJZNUlqOrAKP\n57XkYprfEKmrpfnlWjq44Kes5j/CFwe8y/9wfG/Q2joo2qwvIvp2t/9EcyUv\n4fZEjkwsmUTusuu/7g9SEDYnVXNWDKmchXbm+t8YZunksxvdMxi7vKF61qfA\nhjTzjOEP0kTNOmVtSIaGSNcg5/TmKRX+n4XuDUMbPJYqc9f5ueLlMChDnsFq\nbQPzVIkcrM/UE8V5ErWDr/XUj25sF04NSLYu/W8dM+Xfl2LrE7UfQhG3n1oU\nDBhbm6i7q8WwbKZMzEaBU4qFUxJS4zIxGNwsyXztT0Ad5j6YvwhzKAxLi2MJ\nP0/6pX4cCXFseC+YPk2N/1EoaUMMwAJ4OFUc4QRMdbFZBP8USYcfikT1g+Mc\n7ivqDGeh6Ftl+7D1bwS8ZoCrNY4gNcMFz2Y65czosKVPH8sX1bBymx5wTn0w\nZLCRNGqMlNnr6Psbq/ZMNWkTpj9hl84hw2fhhNiIFM3xShL05DTtMu/jbVUf\nmo5h\r\n=1nMP\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"d7bebbe119e39bd973d398066f5601862aface5d","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.16.3+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.16.3","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.735147131.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.735147131.0_1571189003922_0.004267889686463855","host":"s3://npm-registry-packages"}},"4.0.0-canary.062ade5c0.0":{"name":"@material/auto-init","version":"4.0.0-canary.062ade5c0.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.062ade5c0.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"d83431a910481304939d3f4b500c4cbc77a18c75","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.062ade5c0.0.tgz","fileCount":14,"integrity":"sha512-EglqDCr1eIFx6YKT2x7v4SBtvnZ/yuRdsFc4aq2xgi+BUId3QdRIt2ome/5npmyQYHTlM0E2qQqHOay5/j7udw==","signatures":[{"sig":"MEUCIEkIMF9htVK6QqCz5ORohezhvCHWcEXiznrjAbIicMbYAiEAifg1x6x30ClbS615AuCHMB8JuOxg62sCGWY5O3vgAMw=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56254,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdp71gCRA9TVsSAnZWagAAyr4P/A6RCP0lTwW/awE1IC+r\nq31GUpvbBpfzPXC1GuLSFHOzJe8NKETAtCIWq8FiI2c9n46hy4oK+2+PdL5H\nTV2CajKs3iQsXPdyIONE0KN0nxtCPiYkxrPZxYwFfJIGCiyU7RCvuuYwspr6\nShFiujuQS1QwqgrcK1eEj68gBpn7PznM6ZnzvlmlwIiThuNeVFF2WfsqjiTr\neLqIBNGZqvNXDOvNfdtTuTt1+xLeUKG7EBsb6fJIQQcWHx2P8+OQnHeuA5DO\nHSJlEltWniPFppmMUGBXtlKicbaXmJkxPq+I6w1SOK73deIrPtc1ePYMudA4\nMDOznFyphU1gJHhOjtrwPtlBQpdUX+XEiqL3GADVZeF7pFUJd/9/0url0duf\ni18mbmYbB5RZ78048xNo9RtT/HyKVQ1UxRo6HlNcg3VIasuvCZwMw/FmLUjt\nUiANDr+Oj38WUhknzqE4f4KWFJFNqD33q09XxJ6qhU0jvK4QVhtmrjVhY2jO\n6lKsGRu0C0Inz1zz5n04xGfJ6Gl7lpn8OrPkiFXX759ZLxji1yrd/Ph+ijqd\nsWBlzDCX9ymOJbWAWgiZNWrRNwP9WAvSBUw9JcK5E7JTKBA9bR6LYJcnHqku\nKLjF+y13dHljQ7J/AjoNZjeTU+pS8qxMZzz3GbXdQqPsW8gWk03W+J7W7S6x\niJL1\r\n=NyHI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"e2025b4ba4d9837dcc1063934417df1eefaf29ec","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.16.3+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.16.3","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.062ade5c0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.062ade5c0.0_1571274079485_0.8406887129187781","host":"s3://npm-registry-packages"}},"4.0.0-canary.774ad4f8.0":{"name":"@material/auto-init","version":"4.0.0-canary.774ad4f8.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.774ad4f8.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"46c3ccfad4a8e1bb6e1a8aff277be159a7bd6846","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.774ad4f8.0.tgz","fileCount":14,"integrity":"sha512-2Rbsu6N8bkFN4Bt9oGdEGIPsQ4mhavKoNBjymByUZ2Qkh+fwrFmCpYi1kGFM7f6EmnQLDnw5G0xClEddkd/SZg==","signatures":[{"sig":"MEUCIBfqMQJHQi09HOmGtWyqOFhxAe/mLRGnT6BSUqsGdcu8AiEAzV9pJJbKOQp4rpHgCdVihtxwkFTjF+y5bDUlfYYFdKM=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50326,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdp+g2CRA9TVsSAnZWagAAOaAQAJn0wZak59sivWnOSIJ7\nnrxCmhdY41MWqUX0nK7IoaT+TlUOjVDPzOWPDGuImJ5t3JHo8r2Q50n1KejC\nli0jf1zCu6k9QWTL4juo9f6A833f0Bye0ohnIUb6I3Z6zEff8mtYQQ84laqy\nB120CnNvdKdhbkd4iZNGBJJd2r7SwJMlbjzqBkBVzBXz6Wm/czMG5fOK26Bd\ncC9k5vW1wBcrzl0cgZXxg5SjPZpTbmSRSXkGwZrnq1K93amAJE/ooJU5s2wX\nRr9VIN+Id3AsF9zAu2g9HNJxmaCrIYquty01ZsyzJPi1AbAe8CuSuiZ2a+ZV\nnMVgUPuqXJL3vcQDx9/EEwQcy8kKQBTxfvfVb0QE3QX04FjSbxyGsSKQftec\neW87Agi/0QLpEpMdWG1zK8GkipFwpZTwssZ7rJDGvMe3ztHg57Humi0gSoxO\nPRT4WQtvOr58C+BVHrHFp5ZTAcGBxLKls+Eu1iqxC1pgMAKSEjD/5T8gJsxg\nDqAQPnQWifigPup37wll6YdLSBswlZV5+QigySYGIkkpZ1PbNXx4A7qpWkaC\nunMKCqts+waG8a0DR0T5Kx7rVXbIQlbwFQyvaAv1sEINq35bGWWx4soXsjhZ\nNkFVWtYLRQHPpPbx8HgR/xGMpl0v1l+mxBuT3Ac584Fl5IM4s8oUyaIRYtS2\neMiG\r\n=GKac\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"66607256fd6f9e4fe92319b094d8476583109bac","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.16.3+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.16.3","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.774ad4f8.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.774ad4f8.0_1571285046020_0.6599715041889473","host":"s3://npm-registry-packages"}},"4.0.0-canary.5916d18c.0":{"name":"@material/auto-init","version":"4.0.0-canary.5916d18c.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.5916d18c.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"ea4c4ca81216357ec75a4195f1cdb16fb285831b","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.5916d18c.0.tgz","fileCount":14,"integrity":"sha512-Pr+WEE6MEyhUtf40jVUvspqt83lmKP4MuIF2O4rdYBsThMyjJ9JyV9q5y7w2lLFHMayZeX08RqJtoOyp8nV9pQ==","signatures":[{"sig":"MEQCIFc3fftJx22aQCLrTc+ww7gM9zucpbo0GkKltAkDx3aZAiA7m/wuYM8YxKyW7WM7hACPX5G5dYKsBcjhwfOkrJ5iBg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50510,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdqhuvCRA9TVsSAnZWagAADywQAIhFoaHnBNzqqL/5jAY3\n5XhhUXgfQPoPdw4PESpzS7dB+cZiCl34HHPTWxgkM8JLMMCQVfwkDsudmfiu\ne+mgLRYPfcrGdRSnNYLcXxqE1Zhq+aoOs64RLtAxuPmIu+1iWZuui48RDSuI\npltyYwTxO9iiWMg/YkrN+H2n8VZNDYnS/iI1j3c5yYyXUBgVOkMaxW0DDoTp\niLE0dgH3ku4UBIzFVIOZCGqUuibWsyTC5q4qGvdG56QjQ6en0a4HytK+QxIp\nU5ClC52CojZQKQ2gtNKr8LEkOVTdazGXOPZXBTw6Q18fM2bii+xGNyyCVK9Y\np5YhFMKs+cFZ67DZUStepJonOMJ2b6glLdh82CGV74QRslzid9rPLBypJxmJ\n/wJidDoQb80c3j1wGcdbzLnLTZWSIYZQiXCvsD8cRE9BQdGvKtrd2C5kmgps\nPzPKBnDeDF7VGYRXcLE0kQkvNBf5DaL0cXDkDUuUEAxg0rfKTx7edtro1Y8O\nLECFVQkVaJ7yKs7kKy/7Ok2iQRUYpXwkams2+Mkboxb3MmRRB2WEHmJMs2g4\nRb3TjMPESnZ7/Dj9thWk8CItFoVpCvzcyW8e2BUr4l97Ow4K4z9PDpiYUMa6\nY1+/S5fbRNVlE+Zqa8EqG3jGr405UG/GRrrJzkBQu1oymd8d9hEHTGNi8dAP\nh7C0\r\n=GE46\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"e3338b891c5ab3207ef8340a75490415e30e313a","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.16.3+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.16.3","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.5916d18c.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.5916d18c.0_1571429294576_0.3032285810758262","host":"s3://npm-registry-packages"}},"4.0.0-canary.d4141c95.0":{"name":"@material/auto-init","version":"4.0.0-canary.d4141c95.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.d4141c95.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"abfa1dbc9d27c45e9c821a38a4ab77468015938a","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.d4141c95.0.tgz","fileCount":14,"integrity":"sha512-pdBIt36STxjTT0b6HPD2PGt6Fn/CW5nPW04J4cSz7z47h36evlREuGjgWTqvRawuxRmJAluWZw162eZHgby84A==","signatures":[{"sig":"MEYCIQCkZe3ZxDtg0pisKsTYezP8jmg3QNrIJCbpYsaPZCDOLQIhAMKswGD1ZgwBeCOflzNs96DRp1EMRrlxwo6VEg0V2jOU","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50509,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdsQB2CRA9TVsSAnZWagAAWzcP/jSiQWx2z7zuw1jMjWHM\nOc9bFf2W8pJ0sRQU0FedcddYyiXGZX+m4RA6aANFI6p41unbTNiqvLyOzRh+\nhwDfMbUAoZSnSECTGRmJJtbGhCyAiG0oVXwzGugiEMto+pvM9VwntSrghTF3\nF7jjTPqAssxo7l+yYlHBM/iLfmngDM/Fbp3cjTnF2q/2AeM5HWQ64vQjhzbp\ncmu4jnwEF9upS37IhJINyIyILcLSX59ifeSkghyhRD3tSCJDzBIXMnzyZFwh\nORSdjWvBqIhbk9qdRPodLZDTAAKfcNjvi1mdMVrpbNqHUVPaYY26yu0Mr43I\n2T2ZuvnW1Q9xFZKCzFLtOMLpioUo/aHAdXVrFMII4GA03TSICE6URY7c6oKa\nkQSTBTgnwqUi2I7KczGGQmlFM77tEDcfDWv+YqdxM9obPj2WsHGfXZu6Z0Y/\npsahDmrm+yvcQoNRBZHH8WBx8/kaEpxE8wXKsmG1frGr2rq5+YRIiNrZvfKC\nshEttSEMLdCkX0tVgTBB9SPDikNS15H0LZvGBvYRVOPIEZ10h68WfXahRBn/\nrYLZlJgMf3m1F80jQYT7pg+ypQb0CYYq0hKbjUgBJU3fveHs6fEQo3WRT566\nzKKTyEtgS9w5fA8ORdCXQXNO5hwrakm7DZy1caU3EFdGt+cWMhUYxIgQGHaR\nzqjR\r\n=LuPP\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"10ba5eadec617b7fd2711c838dbbff788d6f209b","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.d4141c95.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.d4141c95.0_1571881078096_0.3275771080469436","host":"s3://npm-registry-packages"}},"4.0.0-canary.2b878b3e.0":{"name":"@material/auto-init","version":"4.0.0-canary.2b878b3e.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.2b878b3e.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"3077bf704d038fbb7614ab5566de15700f0c17ae","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.2b878b3e.0.tgz","fileCount":14,"integrity":"sha512-o5t2u9AICZqH0VcIk+UZaj/3byL2bywFNZibqxfiVz1JCPOZXJBqTt2JoSFGEAgdEoaL10G5I+p0PQli/2uZHw==","signatures":[{"sig":"MEUCIQDFwp/FR3mpgHxED9IeQ2gAjEMzlNsCwELi3sAAG6P7RwIgd7qa6yT4BRoO5bPKxi8381ns7QBfPhDG8IY5kYalhk8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50619,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdslmQCRA9TVsSAnZWagAAJvcQAJu022hu+Uf4bnCLQUqi\nRDABFbJw3z912644Z30/L08ZXBFJXlbB9nhZ4kInlIDq+XkCXOYGZ0wTAeuA\nlB4eku4M+rlOI8kDz6f8WIiBkX6gN6K5iBTvcUflvDD7zmgMGJRX7vLqpGAm\niDsorlEaxHjIfzEToOF5WfcVFjpaqcxL15tPj9k7EX9fMH7MOTy72Vym5Lzk\njUn6Zo5ewj7EJOYHHJp6BvzBzbDpC5XTU2DdGogkzKo6sRFaUjFE85E7k3xW\nQak1JkVfFeutRF+3JPukxNsy5IUssbxEk30iAfVU0Dz0uQg3c6bSJkFqYQ7Z\nYbyv4DlwJV9i4gkFCkpUGULdJQ1L7GlUANGlMyS+xKklsa77+PZ9zN1q9b8E\nPvG43LpNcIlck1yQRJ291SCNvRzYH4H935nX9OByHUvk0Jwzn9DBOhBauOJ7\nZTCaHHnxmdngzFy/gaMzNMIE3yyKH/syNwdJvF4czQbIE8lPnWjt3SA8nyEf\na8PrBDDLIl91NCQkydxl4FiboxIZqGRhxnlaC7y09CnArpt5Vbafvyf1dQsp\n/+2kbiQFnhsbPBC1amhxwhDia8wETpAFQgeRa2LRHpG8ZtjzF90AyBp7c/vy\nJuyMaVuYBAKH+XfIxO+e1T3Z/ItMJzNsHB0HUbbQa+muBkvE663W0IUW8lMa\nEhVS\r\n=CBH2\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"29ace6a085b0e37c6546b4613abba6356aa82430","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.2b878b3e.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.2b878b3e.0_1571969423802_0.8319709252001222","host":"s3://npm-registry-packages"}},"4.0.0-canary.b06c0efe.0":{"name":"@material/auto-init","version":"4.0.0-canary.b06c0efe.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.b06c0efe.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"f76a1cc4502c40e4188e42f5f4a7fb666532f82c","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.b06c0efe.0.tgz","fileCount":14,"integrity":"sha512-9uvJprgXCYWChC0cgpHF+pGYdT279CrdRgaenUpA/5MM03MlbUMxOkTDk4gsDH87yTfCxEd9N7slLIybCLLuKA==","signatures":[{"sig":"MEYCIQDfxUsDQE42hmrs+bk4x2g+SKc2Z9TFyo18st2EwgNkjAIhAIutZpuhyxhy7/K9yp41/Rci/D1z9lNBfBaCNXT8hfWG","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50326,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJds6K7CRA9TVsSAnZWagAAt0kQAIAA+wAdhU1xLElFFXVa\newZXYgdwu18AJHl1UvfIid3zW9Fu/+sXfhJejzWYEXixNHkHAF1O8FOIvw14\nNuNBPeffrYqJ8k8pPWvnFzHqWPD1y6o4jPbdWqng+5bSYF9jaopUR4+CWW5j\nNNbLKnFJOw66o9iTey/c+Wm+95FGEEA0hjp3jijo3VsdaXuNISL472jXC/VL\nOQK6Sa9dedCZb7vNIWEU1eEMp/DJMuFQbjkDn0x/UUdQNELUJCN3P+cSbwx3\nTiw68er4vhzEa9g2CjIfiMJUa3tuDpWnhVE0tgyhNWFae+7lcPSn37gCD5gB\nobLJ0mKkLtyiH++ui2BVhuRpY+TuCmgh+D+rraJrkvv3wPAuXNEmsvop1pCR\npYA71YtxL4tDlF4Z+NsvssfP/lXCR7pglsgnex5J/ISeG1VJHFL0OTZ2z2VM\n5DodcCdpqf/q3A+goP7odYV1qOCsu8uPAUaqh+k3oP6i4f8g0sqRxcPrY6Ez\nhltc8NGHVS5eobEJqMUUkMOEo4V9N/XsoKOkOhnInDQ6PYRtBB+N1IjN9CUn\n6KwhUqqDg5nrv8CayfylFjyW/KexegFIAVVaqGe+AnHVLz3VvfbWR1jrdsYl\nG2IJuSIrRxSkWGpwhSRz3G+1wrU2X4auJ1CMibvEoEnvFHmhHzzBl/BZu3L1\nQ7DD\r\n=LDaW\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"023500a209a10669d135ecd0a8f00995f84b135b","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.b06c0efe.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.b06c0efe.0_1572053691342_0.5425463022520667","host":"s3://npm-registry-packages"}},"4.0.0-canary.01628efa.0":{"name":"@material/auto-init","version":"4.0.0-canary.01628efa.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.01628efa.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"63347e709a540e7a4c6f44e0387f01f5c96d873d","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.01628efa.0.tgz","fileCount":14,"integrity":"sha512-TD/SHspNj0QkN/Iji5qsjXrAX8vlM24pEJug7Z7PyzZDwbgoZsaUf4KgnOejdTAIoBtwDe7cVU9jjg/RDoer6A==","signatures":[{"sig":"MEUCIQDKRXrYS8ypaJe1otZrLiCusYYClVZ1Hr3xlMW6yLB1/QIgZcx+EeAEzs7LIWaKB29BxBKz65dF3jSXbZdEG5+7hVg=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50616,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdt4GiCRA9TVsSAnZWagAAbHQP/RfI2dLZzkw6/nqEA1dG\nNs2e0SItFkI53qaOPMx11Mb+qEZ4k5dH+8Na+1fDACpfDf3domIlSrhBw6Gd\nsFluUKSWhg1LoDiANqAlaT+0AmWT1ScT+taI/q9MfJ7kJ/OcHXHANYn3M/dW\n1w7ZyaW88djW0UObwEWcn85miMdKmzXA2N81dQftguPsaUU9QfOloORKRvl7\n0tYs62QwQ5Jkcgik4Jq0sKeYlULlP48X0wI+1mm9ZrGh5KQ7qiqkA97hEvJ+\n/xvwogdrR/u2wh4eq8Et0fb3SomZhf5+V9UDFvrZuvnRjGe102tWumsV9LvS\n4w4PaXwu7VZyf1aQemxbkgvoJvnaYW8vCp/2vaehTaZ//31SwEtHG+jeUO+d\ne1vA1ADJATRLolPiBG7xSf/9fuDHz//YuYdzwvZZkvEgoO3Fr1l2c4AnctUq\nCcVC+vV+hj3XYGH6tZoyKy+0ddVkUrF25nnsf4F+24phVKNwUg+ZSAz/Wsv7\nZ4WSr+1/AXoHuo1Zs0WfgdUtQxL8zuRFGVarZpaEvfh5Kryxu2C1Jsf+lERq\nBZnxJX7Xd3FRkUxh965Q5NWU2nMh3TGQNLBQWh/hfFvrQQAYjwXA1zTZeWVL\nmm0Oewn0C1nQzHF50ecu1rs2OIDaoKa2pOgC4w+12QirLKdMCCit4no0/haS\nc1Bx\r\n=RX2Y\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"d736a6d7c49f31b52dc64101effcb7cb18ca6cc1","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.01628efa.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.01628efa.0_1572307361471_0.3594265094514284","host":"s3://npm-registry-packages"}},"4.0.0-canary.b5c6d66b.0":{"name":"@material/auto-init","version":"4.0.0-canary.b5c6d66b.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.b5c6d66b.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"4296fe36facce36a660da7b7b9c6653f7369162c","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.b5c6d66b.0.tgz","fileCount":14,"integrity":"sha512-s+OQc1lssxuu+I4QFng8HCKKJSl1pCkXyZtCSJTyy/PftJwEcDDi59KVxPSCcaCx+s5F5LhxrB3UVK5arG96Fw==","signatures":[{"sig":"MEUCIQDPxYLA4YNgOcLaosoiO2yx4PO6clzejgncqR6qia1QcAIgS0Am8lbacJAylzqqsp4gK5JAM/8opnt/Oi63yEFXJz0=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50503,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJduH1GCRA9TVsSAnZWagAA2D0P/iry69rD0cMsS9aTbcfg\ncZm27JPUE+Lrv2/X7Hpr+80z6xNlRwiOfrNRFCleTyELGx6PHbBL+05gyme+\nuvOru91FYvDt9a9oO6akzuxq6uCgJqsE3Mg4bgvZNlSXn9+jdFl0kjaUBn5e\naGZ62cyvdoOZrN0/NsHxAhWq/wn1whsVPHODDJaUxJQAGjFIIGGkhJ0szHW+\nqMBTglda7pFTAEpPbIBDQgNX9Lcw7oDZoSc/5wFPYJCVqkR0cihEcZHd6PWm\nNDJ4dV6r+1n8BDWCiAun5E94xeN3kaRyeCWsoWl3g1HUOt3v+l3gR2AGOnBS\nXTOYrO1gzkY4WAMnTz+IjM/RZ72bmdEXke5UTQ8Bjc1ppyHFOJ7EOIuBakAR\nbS2r29bFaEq7faS2OJMpO0IkDy8QhjeKz2HkGcSAiZTgjB6NUOB+qzP8gKTA\nNVTT/qUYna1loQ6NFfFnjfytRrbJJUGn4U5aCgD3hHnr54smeiriR/MJgkJ5\nq+28LhkRzrSH2FuorZ3B13IqTBFjVwJtr7Ob/O9A9ImwxYf2oRAwYlSj15i9\nyJIBPMrhjSsa8sQPic2tT9EYPhGGIKelFW6e0dA6ff+E5WggLRJUe902T/q1\n5Rob/ItaUCKnrwbBHp1GfW84/Y6uXnEwMz9rEI6UA+bVBeZVc9hi8H/kCOm7\nxmlS\r\n=PHen\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"a29efb24799035b1ee49295daebf1ae46a92b529","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.b5c6d66b.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.b5c6d66b.0_1572371781660_0.22598517001037832","host":"s3://npm-registry-packages"}},"4.0.0-canary.cdf858ea.0":{"name":"@material/auto-init","version":"4.0.0-canary.cdf858ea.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.cdf858ea.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"c80429e036d3dd853998bc244504651987d661e8","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.cdf858ea.0.tgz","fileCount":14,"integrity":"sha512-f0M3W/4IMnouz6xZgu6bZ1Hz083FgwBFzBH6SugTbXWcXf94Dwub/8zIn714aZRpxxB5YL0NbEEjGUquVbOQsQ==","signatures":[{"sig":"MEQCIBgGU+HA+xcXaJgIMzdtTZYdhsiDe+h5QKYJIcHRBitxAiAPvl0ejNrvkcYZi22P+6xLo7qwTq+ZKvdt6nPMQBRbIg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50326,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdvHJJCRA9TVsSAnZWagAAONoQAISwWVeK7TN9Gwhj4gRP\n7OwS5UORoJM9tw+0nmu5LF1hrpuOvL0l56x6dLWQEPjx0rYvSQ9JXk2ovQzl\nCAncfEN57x49EFJlQc5s/eBt+nyvSz0ONCdNfT3M0Z2hDXTWlvQFtRejR8ss\n23te1y/yfNoc/ieCP93ospolihAnQ1Mmthv56FLAKBRP9hM/HDtqMaRrOWC/\njtGre5+SSokpuPPI1gcoI/HZbUkq2OWesRFirxCx2H/P2icdAz/wZrqi/oqL\nlV5iavRCZkcF4pBp6lkQibxCUtEM9uzsi0icnIVKKCczJDD0ZuBWVwFrWnoR\nKYWRMMJZt/sOuHZVVzkSB2vIRCCnd9P2LQs3ODOdIhszn8G35O8Re1LvzP8g\nfu+r9hbJGIZtLn20qoaiFXjJfygg7HPHpht64AWf9sJtHIbiy1meL4Po4PA9\nJmB1CTi3mZ0Z/9XANCZHcjfznUMvujh3rkHTJQsId8rZCNRdpadOHRi+gwff\na5u21FK25NIzKxzQBHCArhkZmBYaEwqzpUnNdjCBIwKlIXjFH3fHKiSyyiO2\nFPrLRbli56dhxApTNQYFZtPP5YJFyXAPzZcZDBtroyN0od+28xCk8mA34K9P\nUFhixi08BE//iSfZx6VFzaxzY0hR+ylvErECZIh5YwMl3L1ytiMgTf/EdVKM\nkNmg\r\n=5YvI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"436b9be1155a7b7c0fd4aefe795809bcebe8dfda","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.cdf858ea.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.cdf858ea.0_1572631113353_0.6118593877729219","host":"s3://npm-registry-packages"}},"4.0.0-canary.719b57e1.0":{"name":"@material/auto-init","version":"4.0.0-canary.719b57e1.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.719b57e1.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"557c4f647c5960addcb1d67be9650d8fa131e2ef","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.719b57e1.0.tgz","fileCount":14,"integrity":"sha512-DLyKMVQZp8Ts7zbkxHZJ3YzqzMiqGdWGpq51P4WADi1tcsa6REdEsl8ExZm7ZinIlPzab0I31SThyRsfH32kgw==","signatures":[{"sig":"MEQCIGGgMQzEh+hIQiTrsIBc7997FRR1ZlA9cQ6VpamQbugBAiA4YANpHi6KFWnIp4rDm0qf7GkaD8DcwhjjGAtrCYKACg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50519,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdvI8JCRA9TVsSAnZWagAAvLoP/jjWOdB9YfQZskWfTINr\nr5HBoHDR73JfvyFdd9nwI5jlKWSPSafcAHvZFkBvkEbMzDXk8CRZuNyMqzxp\nM00UB1lvhUHlGOf5wAM+LnbpoRYphwCHSDq0HWsndnYDt7aH4jz/fa7DzUEG\neQ7ckQ7Gnjkefptodwb7QIDWazNv4vJ+CxK4zHs8j3nDBzsW9xKPOlk/7hxn\nTu1YdWW2+P5dieRi5vsi80oQhhgxfeIuB59H5dWZ7tHF5jsI9vFMETqbpP2z\npY0s3qiHL9RxNNTEQz62j5uCxzjV5BNY9Xdvbngi46Yq8l/mCw+VmAZ/XFhP\n6SoIr6IHnFbB7dtE0IZcKGWFiXcXTzm8KghcoV+TL6l1lwEwfZz4ZVQVYqxa\ndCrZpUwXNMVWI9PMsWQLrOpIb6W7COV0dNBkfEJbmBbUHXMZSuMSyUfuKaq8\naAiFhNbyGg9Rv4W6NTNtsemSaCqY0w51LF5FzHeJrMIXUesqPooaa2PfRuIT\nonC5bGK0jLWbKir9mYU+gzvvBIGzBZhL/+BsXzGUZXhMD4bs8rHcXW+riAaA\nwAgD8aFw+7+53WFqWh7Cf01i+l55IMZZ/acY3g7/adtTOM7WpszC1d4Ibg0d\nwYFd8ughuauz4/mxmLMyDxhd5CZ9td8K3fatn5gjn6daJxT0KrPd8CGtMXsj\ncPiL\r\n=awT7\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"4184aa06e4862418697a150eaf45a13500e1c4ff","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.719b57e1.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.719b57e1.0_1572638473315_0.55759157199797","host":"s3://npm-registry-packages"}},"4.0.0-canary.97cbbdc2.0":{"name":"@material/auto-init","version":"4.0.0-canary.97cbbdc2.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.97cbbdc2.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"29c9ccf170d97274aeef7bb444b43c1d3e2e445b","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.97cbbdc2.0.tgz","fileCount":14,"integrity":"sha512-j8a13KjEPaoWQKRLvkTZcuwbPEffmiefu+Qb0dA+h66NZUmDObY7+snpb/TwHKL7gZiW+evz/UU3+cFWLXH5Lw==","signatures":[{"sig":"MEQCIEtg/S83UR2srzQCbbi6IWQjept0MzyLuBwSwQrg/Lt+AiAEOSeJPe0O9g5WhErcB0n/b0Cr+Ugk7tYDVO7iEs++8g==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50532,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdvJWCCRA9TVsSAnZWagAAAAsQAJSpru/8ytw37fxXepXS\nzR1GWWFRGvbMBef/JGDTNhCTp/DbnFkpAfA4d4ceCBiGSkAN+FS8YlvgQPoE\nHlmyaxWrAaelwi+ndrwZGY0bct1RPyUOTjqeIJJ0rKBMb6Jfgbig90bngawI\naWQS8BH260J5TuQEIvSDXUjR514MK19FtedDiDCJzRZLAtPrgFHjzu/malNq\nBhhwX0STQT6JUY9yYP3kyvt6yPS3g5JSkSTJkjPLpjJ3Nz/dlIcn/EBescm/\n+FA6klUtIJKok31dEC8UYPIfVwA8A3fqaSO1dY4enAED6iGklRrgSYCo5cFE\nKmm90lCpI8TnldsxUlEUNL0hYTPfLXyZ2Fl4VcLHCrl4EAYdggBDOZtG+elm\nlXRxmlSDj2mlmJn2lTx3Ck2ifSo8auzGyJU60wB1ThmSUjCMSvowHH7sftuu\n3yAnmJiz30YGLLG3Bn70FoP4vETScy7VJPQxhk0ZpWCjiraDSaLH5YIxbqkw\nGVppsINJUc0lxu8JKzxZsZSf/dD2wmVHdG2qkhwAnDBPFa417nT3zCwqTbEj\n8vSGmi0wEXfjzVtcQ2hFgdwPlSgzUYjvsq53kOejr6NmeNbR4Zhznd+0ibtt\n6iLU+6rWumys2HQavK5ZIGOe42z/puxfcJxTkZPcBxwn/ptC1vdqTbzTeSYA\nO6nh\r\n=HrgM\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"49d37bbcdfa0f5872581945f58c03e62abb97090","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.97cbbdc2.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.97cbbdc2.0_1572640129757_0.4027889683210357","host":"s3://npm-registry-packages"}},"4.0.0-canary.8e36b3b7.0":{"name":"@material/auto-init","version":"4.0.0-canary.8e36b3b7.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.8e36b3b7.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"f9efd1aeb9f7c7abd12017a88f30ef0592c05753","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.8e36b3b7.0.tgz","fileCount":14,"integrity":"sha512-ymAGP208MHcH62MI6ITb9t1VNzY8odfGCBzXayaQlceV7U31mfQ0kwZ5Fg5cJHsSM0xnOhGyzcyV9Fa1V4Xehg==","signatures":[{"sig":"MEYCIQCszEKzULB5ViPyv3Izq3rfLHdK8VeZHw/OMW1ZTH/HtQIhAPTpv63f8d/0noMoGqJS+K9xuUDtusiw96C8gFP77eP8","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50326,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdvJ0DCRA9TVsSAnZWagAA8BwQAIoQAVTfh3uvUbffq8Bc\nb4bqjW/hLRbAZ1aj6Nll6qzpxSj+i1sWVPS90wGtdzqRvjQR0Xc09JV6QClx\nxXWEVMIMsm37GnAfuw/QfhsFZmBq4Vx0lSS7nRDiQhcSka/ly1PvmRoQU208\nojgVkXIYc/mISrq8oHjy7dYoA7ovy9xSHRDVTmbWbWBlv6wYR16TjSG4qTnA\ngigauOpQ88tFsqjSN0bFcXxbZsE/9cpIdGjE3FvXQac8gEF00CDVDOFPHDs7\nkp9yAqu37v5G0ibV5dzDCwNh+l+v96Lt5FSsoVK0/ie9veyhZZ9/j1oUy3G+\nm9O+zKzYintH7rvC1UXJboJEuj7lKPJtvs/jl7rl+CmqCfwLPW5bE4kpH/CR\nk6bXLZyOvdIxGYG754OLlBM1M5q0+jXHMZn+5+Vr+IZS73gQDeHfqkB3CsjK\nF0d6MeCAOIN99GWe420zChIworCp9G1jz6Z+rd+05/Aih8VRM3jrrDt+wU0A\ni6UYShpn02TWUIbB2gQYxhAcLcTADnteZvnikk7fUImZnzVaDpWbS7KbDH1S\njPjYyPO0tBFDOSZt/6IzprAZNPyffx0pfE3YuYalUmh/KxTLoPRuWm5j55g+\npfQsoGksbK0YVV6937UBRi78QKCYf2kAoaMZ+xhYMiNCpIMYKwEn4B5hQQ4c\npNJQ\r\n=re9K\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"62f51968b94685823af7942f779c63658f2b0350","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.8e36b3b7.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.8e36b3b7.0_1572642051475_0.528576190108847","host":"s3://npm-registry-packages"}},"4.0.0-canary.62d3a09b.0":{"name":"@material/auto-init","version":"4.0.0-canary.62d3a09b.0","license":"MIT","_id":"@material/auto-init@4.0.0-canary.62d3a09b.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"a94a5192a4c163f4aa635dcaddaf473afa7cab08","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0-canary.62d3a09b.0.tgz","fileCount":14,"integrity":"sha512-5kogdEGg3gA460uHqoZOTFhpLXpZhwyqbqBoATb7EggxWxQEIGDIShVG+rUXf/t3IAWXm8GIrIt1dl3Ma0jrrw==","signatures":[{"sig":"MEUCIArwuAtV6eLy1p0e3ERLHztoJckSU1zBlKkHCfFogp1mAiEAjueYjc+vxFpH95D7QRs997tC984Zb35MEJUeHrV1s8c=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50326,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdvJ9DCRA9TVsSAnZWagAAs8UP/0aeWT4Y/BRJECIM3Icr\nrdOk/QW7NB7bcKlxOb/jPLQPZ+sSpd8IxhDgunJTQSdq5gv6BcWqjgESffFw\n6qgJVges5thDbzk7R2GAaT4WKNhnJ4ih3z+IRb9E7ZbAzSahUR9QnKyL3Scn\n2h4OCSWBp1mREhmvtP/8sPBwEMEtMN6iAcnVs4R8qLrkLBQi22vB0/rwaQFY\ns8mcIRvxqvEiTz6sI8hWZ0xFkBtUlaRxjgOEIoeufmPxDnoDlBBXAtOjSvLr\nlbxGg0wSBWljNbo69dUsaNrpu2THSNLzAgfjoEbFp65y3ykU8EXPgPuhNUvj\nssxG7yTKLqVJ/g9H9TiG8uo/qvxWlKam073Li3MtpZwA4xD5OTmR4c4UcDHU\ng7ZwadXbAj9LqhuLgzAoo/lJVWPvYgYy3IeSGwgHlXJA9hgezRrpYPrrmlnT\nWTPcY1Lf7XZxMb1pY2vEiRd6tVhmX1NKj93wjRhDiKDLqq57HfrfWvUfmUUf\nbU4d+ZXm584sTb1HWjQod0vWBtjlgjRlky6dHzJqEdaF4RkD4KuhkRYxPIx6\n+u3BnLHE+CW9kFr+AGD/Tfn8e8VBNNX5HFfs0sCOjAAefoqeDoCSHerOJEa9\nmtjWrKZgKzxP68XCD5LLccDmtPeyGQ+lHW0fhl+2gDFMn8xrbs1hxoKwwWTt\nKJZ+\r\n=vmY3\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"e00a9686a58b0fd5ec957d4008b6674dafd4dad2","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"4.0.0-canary.62d3a09b.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0-canary.62d3a09b.0_1572642626748_0.9761356069999656","host":"s3://npm-registry-packages"}},"4.0.0":{"name":"@material/auto-init","version":"4.0.0","license":"MIT","_id":"@material/auto-init@4.0.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"4c3505154610525960e46b81e3ed0b3bcdaafd81","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-4.0.0.tgz","fileCount":14,"integrity":"sha512-B5hCY24cTrK25in2bAhLgsZry0lR6El0y+uxL+2spqGF1Novz/G5UJu3v9z5cycc7DZhZg9wZQvF6tmagtNaog==","signatures":[{"sig":"MEQCIFTSXWey9WRcZoiTbPiOtQAGqKRM1xuT43w6Pzl9lF1/AiALw7tnhZr+nemIHmP7MBQTfz8VE19R77vjh5N2GsWkgw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56394,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdvcbSCRA9TVsSAnZWagAA9vQQAIdKJkL/dfA/vZJ45ylb\nJoBeK/n0Cewxgylr6PeiR6b+a1QYNQk92fkzUInzyp475krqezuZcFCMRmT3\nj0yINWAD9qh3HqvAKdadkHi/AsK5mvkLVn6Kq8yHdNN3kUQihEwCRjCPTmYz\nooD+4d1rRu05+T1KzFMM4oDAd71yLXB5LxNdTaz4SfQGlgiMKMI/8HZ9q3Cl\n2knruEyP84jUiJuhVhEmraems/Kp+FOtqGY8o94H4m3YvtzCr59gLqW4PhRT\nVLmK5hS1KGC/6bqUexkK3Yc9HkklDhz7oYhP2va2Zx8FRAaRkxCZJulRYoxD\nM4NsQ+D1HAkfV66+1HaeeoCVRYHBJIXYNANUCtFM4wlLWah84NsuNwsm+lbK\n+Gf10tWNnGn+VfL0d1MA0Wnvpjv7X4qNGp4ClXa2NIQp28ZVnsCHJoM7JXXI\nXwUEdg+7T1oSTwJEhkXpe1+f5Yj/P69E5+C8Ef/QGv2lJBoQSTlcvplRoHmN\n86ep+3//BqW0QcnZqvSKni9Xx62F4c0ydXJjo25tqgS9H6lluZ3VC+2L7+Kr\nv0jl+Yqnoeiwx/HUUjAjus17n0PLPG5RIfg7np4+p7hdJhmFiG/f/BU1u9/I\nqMom9h8Rs9rfHNMzxeZWlAYn6YIZnkcPU5fZiAcgASc80SM0LFJBiTTlgAxh\niY0o\r\n=iZpV\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","gitHead":"8fcbb009cd3b5cc004b302613dd55ab4b5d6ef72","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.16.3+x64 (darwin)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.16.3","dependencies":{"tslib":"^1.9.3","@material/base":"^4.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/auto-init_4.0.0_1572718289607_0.6586549647574196","host":"s3://npm-registry-packages"}},"5.0.0-canary.b5eb51e94.0":{"name":"@material/auto-init","version":"5.0.0-canary.b5eb51e94.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.b5eb51e94.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"5beffaec520fe15c46b016cd6f94be1c16422026","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.b5eb51e94.0.tgz","fileCount":14,"integrity":"sha512-Bi1VlsQmJW+h4uW0OjGUZa//TuHKyOVpYrvYSGv/17ctLK4lxEjXlQU7L97dlsPEUGdbr9DsmuIXhxhFAe4gpA==","signatures":[{"sig":"MEYCIQDu789xGMwdOW9vHW0AG1/dc/oqD2LWx9aWt5Mpg8lb+AIhAJscFr4KMe9NiTi9A3LDB6tB0kzqivsBtd2uGAe4kqOM","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdxGNxCRA9TVsSAnZWagAA3zMP/1aenaRGPPzlmJUVtpD4\nSXOTb8ZwjOdV4h6xHxBmtL1VJmgx87U76PDi0ogNQTevPhkkmPOx2T7Ud6NZ\nZGsci/iHLwM+ZKMYfiHAsDLrpJojvpzpGEL7db9MkiHA2gqvdH+nWukHpjef\nr1Xo1PQZFzdvCFkHzW6CWqmQs+RlSGa6Imd3a8kHqYPqSnrVAfSmGczIYoNU\ngxJZi721fnZ+xVG72smRVpTH+7rXXJufPJXWdu3tIsP+JuukG258XmYKknxX\nj2wTXmgxg3PKWRoEYywibHIF8PjaLCjKpSX6olJOy3sj7ARBj/5MWxr7CLQr\nJzT7Q2x2irO+g0EMgzdhngMZzWWdS40IHkHpwEO9lOp22P3Ni4rEiym5NEBQ\n11siQIB3HeBeXRdixLAkAh8UxK9/A/9gcktmUIJR+QFY/H8sBmMcG7KRXsrW\niYOzUz+AuGY2rjfu4jnKAzjdj+djz9PZBHls6czttRiq7pnSS03vtbRDpz01\n9lI04qVrdbkGHXFyDs5qyKPZzaTQ8NxVxaq4fWJqU/yuiw7vkNIG19rFpqvJ\ntIhMPTW3phARh/EIHpxtM//96OKf+kGqVVHSB3khNBcezcwt/SwoMkQktwer\noDYiMeBQrpRJ591NYifO7VDLOTyjDaT2i5vN3vpZz4OSfdEO5HB5i+cDsKuj\nhLOd\r\n=w4YR\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"7e8d43f563cf6b162c2aed47d2a006564994e4d2","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.b5eb51e94.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.b5eb51e94.0_1573151600629_0.5590306450306919","host":"s3://npm-registry-packages"}},"5.0.0-canary.58500806e.0":{"name":"@material/auto-init","version":"5.0.0-canary.58500806e.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.58500806e.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"443c98c00708454b701a8a84a93e04691f4746fb","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.58500806e.0.tgz","fileCount":14,"integrity":"sha512-kBlLkpzqpPPgJgyDT6Dlp6lqcDFqQ14LSv2ckXoMmfZ//QQV4jkInd5EBdccf4wDrshT5zEkZpwN8D8R60nKKw==","signatures":[{"sig":"MEUCIQCdWBI/xGbumj7wezqzI1fi9UPyeSboxjYDNG7EpiVk/wIgBXCEq5qvGbiWrK1e/Eq9OAdHV+yjUQK5umVFBAgSXUo=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdxYs6CRA9TVsSAnZWagAAPCQP/jqhpanP5x/lD6C74T/d\ne5cjvb1gO4gtPTp7BwVsPnA6lhh/ff6d3SuhEnkjhAMGqePKSdOQl/w9FA73\n/kyieIvHE8VLJNBQ9a47dknYBqXmNT17BhC6osV0ymHAM4VlDIw+wsuqEF5x\nuq779+3/ydfp3+xnel6ToVSQm4JD4lv9+bTqM1QF1FT1JlIHAVMLBQC1Ftnu\ncm3gJb38Hknf7Oh/aqAXYw0a2rkFT/NDRNJDdmiIBGOW7Lu/wQN0i6N5vWlv\nf6xHBEdWwxxRQ1z2WXJ3v829b0n0P5gcxdYmvHb73ztWAg7wkglcddJmUK82\nqKaH9cLxXv7BZf01vG6+qm8rj281YCyRHFDyaz/EjJYv2mdrSGcbTlT0kxWC\n6n4pTRZ2AVIaeqpUbinQ7nR52VRhzKxb+2/gKk4KE9JWUNTZzbfEu2nZn7gv\nErdDWm2qUBm++HNUq4kDSdqYQi0c2f1D5bxXT0CmstTgep69o7ZGLj2LCZj/\naTiuddFP4Yd7igrb8VyxvsXNC3AGR5Q0FJ4jOM0+/lqS9PiGxILtxu1TcybM\n3eXCmH0sqVKo/4eTYjr0CDyk+PoCt7s3sGSSbIFzf4RVEp5f8IkP96UM3I9f\nJKEXJ7+0BxSM9QYPOWa9ZG6Iz2Vu6AewD1RtEd7eJJYb4BA3l9j+hJDfZGea\nM8VD\r\n=plrP\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"b155f26dba1f11e3c9d7d0fe036cca6da8b37a3c","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.58500806e.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.58500806e.0_1573227322215_0.05644672052088029","host":"s3://npm-registry-packages"}},"5.0.0-canary.66299b646.0":{"name":"@material/auto-init","version":"5.0.0-canary.66299b646.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.66299b646.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"db7f6784d3d00cb2872fc6e60cc94d21be2f484a","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.66299b646.0.tgz","fileCount":14,"integrity":"sha512-SBklgL9NG64HFoKXlATt5pqucFr3QS0+Djkxz2U0OueN/H3BiWUCVGdNCBnOeTL6W1bXJbEqwzHGR/VbJGJf2w==","signatures":[{"sig":"MEQCIF4DiUE60n6vAcT3JIjyI7a+Nyg6zRwL09R3ZZ0+OQMNAiB42op1AcWQENckbBPUgUqol34laaZhaUMEER2780O/uA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdxdEVCRA9TVsSAnZWagAA67kP/jQq/O04j/YZolVHpUCG\nOu6v4WK2GdhVIw8FvM1M30+ZgL9kXzCKfZZZa9h2ju0/GbgPyBYQTuErJe5l\nLLPErU4LplaJanW9Os4UPHA9EuMCjfYaSuBLyVbkRAnxV6Exuc/q4Bx6x2+o\nnm7/JnVbgThtE91BBmdBsdBM+FIfJy8SdIWWsmgQxhnz036tHDFGHhigXVl4\nd0af9Afutd/4pq3lx4010wM1m7H33fZGyY+ji+QPUPo+OH67QdFBu4rPK2+D\nJ49KwslyvD4l1BmUv6aAjckOVElG8xL+BXb6XsfW2LUUuZ0MUBuGl/ffi4CX\npK9xeU19Fx72JmqWr/TGFeLu5h39OqJI7o9mjhF5drQLTjCfb9fzmUhVZXc3\nB9FupaZ6UYvX4GpvFafyxUqnA1ITmm00jitFTLQIrGcrTRkmsB0Z8mks7xl3\nCw/t0xZYttKm2dKG2KgcOrxTlTmxQ+s6Yx/ocBqgOBCAWTOGPFTHiJN9hDV0\nnEEe3W7tx+uBG9QlAHNd4TqfJoShXorbM5LNovy3k3ITZp/XB2pAXJoAjDki\nJwGhNrBGWJ/mDxbPzCbnJEOig0dA0Sf1J54oAMIVTzcah1p0Wh0w9w1fLtEn\nR4B8lvXxWQ2nz8n7cYtOMGB/8lCEdrwOoYT5Erpx4RVg8xbDxEIwL7vww0rh\nyzLM\r\n=Jxg9\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"4bcc7c183ed18cfdcbaf564e317231824ea91b6b","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.66299b646.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.66299b646.0_1573245204739_0.21098519743151933","host":"s3://npm-registry-packages"}},"5.0.0-canary.821871e04.0":{"name":"@material/auto-init","version":"5.0.0-canary.821871e04.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.821871e04.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"3ff95ae7369b92a9ea772a4cfb3f35824270820c","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.821871e04.0.tgz","fileCount":14,"integrity":"sha512-oVPoNnaFnI1+pY2enzq8bhfsilkOWz3FsVs5nYOJD97lnywQyFCn7OopWgIELWZHWqpGrYU9bxiFjK/6nF1c0Q==","signatures":[{"sig":"MEYCIQCCBYwVMD6iUnhRUxA9A+VJn+seZcVBjUvpNAtUMs91zAIhAIRpg5qYknQbs9yCBj6KWdgv/uv3JWE9YI74gH26MoMr","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdxd3aCRA9TVsSAnZWagAA1jwP/04L+2heuOQiFwd98+ll\nrXw0xJBvAXv9TWnMG+UAW5/hj7beXZeIcHMtUpexn0pMl02kKZ80NbGQgJjJ\nKBlraXXKpSlTHET8CA2B+IQDo6ea5B8z3SN2cBGqHyWGWF7d0bfXrgMu3OPm\nmGWcOONGdfDphYoVyL3UG0BYRAwJWFlGbhGWo6SxBsofPFOyAOYwRv57Ye/a\nzDtWyd2gnYm6TDO6e+RtBTtEO/6OUDGQGTvUlgcwXQTfuGnGc7HLDCEDE2/h\n9p01tJwbuImti+WJBaqOxqGZG4uP7+rywpV+XaOUM1FHWTvdqaF1AZSHNBGg\nIFtvOz50hsBTpt86VNpegl3e+eVYzUCNdmaHPwcoI0qcNgctjWCmv62zsSfZ\ni84KYXv//Y/9UAvgrG2+UO6ArdS6bf1pu3qUf9WyCPBjCIUTT2+5/8ZnXmkj\nNrq5QlkzUN/UGZc4b01RxgjCuBFHV3Pg9JuY9GMZKAWTjOpN80q2O/Bq52oi\ndouvXWy/FA5vdQJ4K10ssxaPVnBGdahXtGMI2TALjkrOnkjDBu+vNgMKwf9Z\njZyXAbORndL1rAoqDcYd/ylR4ppLOCHLSRJLNoIuwhngc/hDwEQ65LyiTuTw\nBo9P9pByTmu1PZmgrADPc7fjSy1ghXnVZLlk3Q8D8tMRJD4jBoHBzfseVJt+\nqVZe\r\n=yVvP\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"20a91d4645dd0fd2db7a61459d752f390e050899","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.821871e04.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.821871e04.0_1573248473952_0.42190784264272674","host":"s3://npm-registry-packages"}},"5.0.0-canary.491fddc31.0":{"name":"@material/auto-init","version":"5.0.0-canary.491fddc31.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.491fddc31.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"82b0608a3a012e62bbf693bbb6c06478f753ccbf","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.491fddc31.0.tgz","fileCount":14,"integrity":"sha512-EJrCEGmsGDdfN9IAaZDwxYRgNranqmb20jc8jXWEsIcS6ur5urposc8EdgFruJE4pYVX4jncU2IVe8RSgBh66w==","signatures":[{"sig":"MEQCIAIZTl6/8/a9eY/aqNWFzP8Dxl2DHFhnMt1/PDio22/dAiA04zoHNFp2H1VgdU9yhZxyvWfM727hsqPGgEtcFIZglA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdxeb+CRA9TVsSAnZWagAAuPkQAI0P1PArYSlrdqWnNey8\nGeifMn4f09zT1dWgeusS9tpUdvlc7BZ90plvRYGxq2pjAinl6NgZvDVSXNL4\nniHjUgHxPLDWfH6qIYn64VW+3QPzdzTMlv2eQw1+L1i9RDzW5zpeU+3d5jJc\nDe+m8samo/szV466j9vRFesMjwsfJd/Epmw0Egn9mvPYScWDa0Zxmta1FqUj\nS+6BN4/T2tklZtD0k5aGdCiZ+ApSq9jJpfcDaKWXu/FfIEclCm7hpMOtHlEJ\nmZjqnHDB5sECqjM9CCjkwRFTtvbT7bP3ESdE+ax38Mr0zEoGiSyX20CJWcWZ\n/izwXLxr6zlMaDkzZe4MRbZdApe11Ih9q+Uu31lyOMNMQWERBRR8eQPx1uz/\n+zs++ylxt5vZflGz+zJlqz+nerUT2v2Puesvg19EInLV+i+I6ttMez2ojgr7\nkVWwBGv19PpxM3/vVbbXWuhq2iFBVn0mCRnX2a2V5mjMF9mnNwe1sXz5WlGT\netoCu7NFGGyIpZ9b5C8bWeDZiL3rba18DCS/MYWKSi7KyLGUXaEF0eetSzb2\nEOHSxI9wnJQjk8e+7YFyzS0abaxqLrFZqxk29PQ8fgpuIoZP0jv+KqrAdJDO\nrgfGOgYRMHIdT2abmHo43dnsDILYzbZl3Jnu6ll1IiYooRrxMi1XLoqPsm/s\nxhaY\r\n=PayR\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"36ec62985e32e24263ca2d444e04a01d98ba02eb","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.491fddc31.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.491fddc31.0_1573250814514_0.538458996703167","host":"s3://npm-registry-packages"}},"5.0.0-canary.b0cecf145.0":{"name":"@material/auto-init","version":"5.0.0-canary.b0cecf145.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.b0cecf145.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"c2c4f0e97d449ce649920431164ce3c1a07002d8","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.b0cecf145.0.tgz","fileCount":14,"integrity":"sha512-pmHCh0kYeJfNc0ZW9HCu7L/BxQ7pwt+8iyAd9TqmiHFpJ7vYLLJvN5cn89F5JzAMcc+424E300uBQroJR/GF0A==","signatures":[{"sig":"MEQCIFNBwwP5eFXFlSVDVPvwrAOLrNXWqPkteW1UTlREzEHEAiAUCsnnwHxmQPdotz6OHyds67PXX4fIMz+ZamenmGlNQQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdxwh/CRA9TVsSAnZWagAA5QMP/1duNxlPNGI2iryATd9S\nozo6BfKizOahRj1MVHCSNLZsmC3v/QhbUiiA1FP2gRWkMPv/TFKVgdgDaLGv\nYV2hCXz1hlBEI2eISeiKj3SBvem/t0k3y7RQCwA9jvG0FPOPljRi4srQoWgC\n7HLQkokXr4Shprok+VtVYEmS12oxok8SYJtTcZKyxljWYXH9LDaBLRs1nU9Y\n+KoYlYf/BlMrkryYqFaD1WXN8JqvYpXlA4rdMBPIYWhVpAUEk32JRRNcE1XY\nIB63tZGX8BGLeb1SC6DdKacZTje3FebnYbRCoGqBJCi+TpxwP3Yvi4pPJYJV\nlL4UmpyLgT8EsOVP0bd/cP6UI0AoFa4csUQq6KzJoRl9CSisspnfgkJD+FQK\nWOzKueWE0kVN13GOi80wFUo6sUJhJ5WZbNi6YwUeh/uxJjSxndz/Qe/xUaDC\n0VT50ld8jkPbOeH2kHgO1cc/NaKmyd780/eb80whhVHI+iTpMMACVLJ43BLf\nAalI8HDZTBVTewBRXfZUT/oGxSQ6NAgatkxgQKMlCm7NzRu/gUHF2LgflAJc\nVW6TW11SngjLHMT+qTLRgSsiL3Mtm1xm5dZeBTYf/0Y37d/kUYTsZgdlegrj\nxqRT4vqWCyjo4uHizoWCS36GJC7gVQ6xULsFZrvn8blEDNFJPCjbS9n7QyH7\n256S\r\n=OW3x\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"c20143ddd0d46da106e793fe5b768b628d433923","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.b0cecf145.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.b0cecf145.0_1573324927153_0.8076884810201614","host":"s3://npm-registry-packages"}},"5.0.0-canary.afe0dd1bc.0":{"name":"@material/auto-init","version":"5.0.0-canary.afe0dd1bc.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.afe0dd1bc.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"e0fdccf42989a6afee51a8948632f00fc63d13ed","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.afe0dd1bc.0.tgz","fileCount":14,"integrity":"sha512-vy0rx8gGhIB/8DSLC2ARPU3bBScu0FF3z6VO8s9qbnmNYEvtdqZZH9lHfCVDOmasJq0hTjWw2PpUR8Z880KbeA==","signatures":[{"sig":"MEUCIE13YHUITpF1I+e9NBx9lkSmtjMT79ThPtujqappMzOnAiEA50swu/xZgBZio545ALxJjfxzpJdEFBp0MJnugA4EeJU=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdyYA1CRA9TVsSAnZWagAA8QsP/0/vOh/SdRD2S9e4jWJQ\naSByK/A8zhWnNQvs+lqB/SYWeakpyD8cq6iXQzmeFT8UjsdFxguBzBH33O/R\nyesRxgBoSlnBUrg/1Dw4Std8j8Pzb7ZtpOEHA4prMTclGH2Ktpoy/eaYiJNx\nULBWcjie5d9ueWM0DbFfidsPOiFSVOXODCg+L3RsmkZ/GVWkqwjUgFhdObV3\nvtgKASTnT2IEnPcEIA29JhVDT4Jisqhml0xsH8j6IPCO2tcWT3z5dVK+ILBm\nsuzkJGYwceZwmyHE9tSwTbtl3GbhNetez+1aT5a9z0YikxxqLqsk4fdsi+Lx\nGRhwZ0wcirZRE8MFxc3EitQfSr8961V/cq8qK/wNg2joyqXXeW2Pi5kX0S1M\nMoRMLZxi30LDRoCL+OMhxjDvaNZ80+YOMVFSaF+ifNf1xQXquZqX9k7hT3BB\n7zFfxU+NG5xkAFnNcgQICQSGehZzuG1+qZ5VaQNwAVdrU+nTyzB3ajLdd610\n6lPuLnJqxnmGDTKxxHLyWgdLlHOtIPIyZg6udyhekPg4YYmsKBHJUhO1qrVz\ni2PvCxTRE3qGkQ8z+PbntBWW1kmyShoKjV09XAzdlWEHh4WcxDFgcoYp+Q2S\nHGbvgruhKoS+5IqCa/ATE6HwoB4V/C6ULAfsuJgAvga9HkFbC1B7i58mLSwx\nEH1o\r\n=h0wU\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"3bacd69fa765f810b8bf40608eaa3aa2df12bdce","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.afe0dd1bc.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.afe0dd1bc.0_1573486645241_0.5094719169176662","host":"s3://npm-registry-packages"}},"5.0.0-canary.b4cfdc40b.0":{"name":"@material/auto-init","version":"5.0.0-canary.b4cfdc40b.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.b4cfdc40b.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"76705d78a3389d3e870465a3724e04d234f1bd43","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.b4cfdc40b.0.tgz","fileCount":14,"integrity":"sha512-LeKaIx0a5i3EsuC3KrAjc7jP7wPBkcp9DROvwXlVnC6K12s4Ptj6Ya2fQm1jU8ZTte/vcaAuDz4KSopkLIo6iQ==","signatures":[{"sig":"MEQCIG6TqWEAXR31xwiCZr2EpP0nH84YrSbShd8xpnQ/BmE3AiB3nowLQHZ7PaR+TyAJWiX4hpYolRLe/JfCXpcwK7Kqew==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdzXmRCRA9TVsSAnZWagAAh6QP/3Rf6txFdMC1eiW+jIsv\ndWUn0s1CjxmISQvynO4O0ZylVOn5duy26QPRxneGlPNUNh7Il8PWqiSmn2Yd\ncFSPOe9E9TBpPMQqkrtfNO9HdxZyIVwaFrpFyfkOdp+jYUV0ZLFTmqOnaFzP\n5/3DQUinymsJ3+wg9tB9GmT0pSkYzV1CtVNz8t/STYoouYmHQ17JyRuiYNrA\n6ZcsQfYAZoJD5i5KSDeRdf0DPvHvD9TIhIXPt3+ShQnQcZ/UpOiTMoYgyaGO\nuEs2ThZ3F9ItxuGt2YSY2i2xR4vpKBxAeDgm56ca3Mf+OteGzQUCcGcVnWx7\nsSiEMZ8rHtNAlT2VctT+YgE5HoMUF1W4tG5PY1v2Id1PLJdnLp4j1lSsJOCk\nq0Di5VDeJp5UFFEgIZv4E9+6KtS/yqNpPNXEvyFEzHwNuKSloLAE6gFkzAmW\nP3IWnJrxP51sqDKgeOCQ5QTwAJQp3/MXyWjRNnmtJo3XZko1NwO0eBCf2NAU\nw86bpDuxg6PHkEmiwMAZW18RneF3dElpOLIiTl+VY1bnvRvHZ53KWeYoVg5c\n0tw5yq8jcr5Z+XUQiHsa2MdeV8Ig7vTXrbHv+lLmxUcLXARpI14ej0xSAkIL\ngfHUwCYnOGa7apMmvEPxTzm/CAkfsQ2GDSQYe3PYqoMCcmRZfyBVO0Uyu4v5\nO2WI\r\n=P1tI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"2a81ebd1a573a096ffb378bd1ce7bc223a3cb54d","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.b4cfdc40b.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.b4cfdc40b.0_1573747088649_0.1773473052322052","host":"s3://npm-registry-packages"}},"5.0.0-canary.525989b5d.0":{"name":"@material/auto-init","version":"5.0.0-canary.525989b5d.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.525989b5d.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"0669054ac02cd02ba78b1d4cef5b25a72d3b2ace","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.525989b5d.0.tgz","fileCount":14,"integrity":"sha512-G8Pz7/lZDBPXY2R8fWLgmPcg2VLUF3MJkwT1Aze99wXui/UbBugWuV0oVbS84vCw/xGJW0Fyd2rzPgY+95TWgQ==","signatures":[{"sig":"MEYCIQCow/vm4ceIsj5URmBnwJDModc6ftSODLkG3cwKZdzpXQIhAJT22bi2zbknAeG2vYvt8Ha27HJwVd40p3pivzcymk8Q","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdzeOYCRA9TVsSAnZWagAAfM8P+wZ0xKh7d9k3gg6ZEECZ\n2MnPJhGxmovq/pZhHWJazf1kzhxSbSbhUcGpnajC/v0xpYnixB7Czwwz0U8G\n4WHi/7+iEBNFdwLoc3NVfLBJCxkEqLf6KAK2UGgedDU1FbJTnSIpz06ST0Lb\nuLB02oh7hW258nU79brTwLyRVRZOdvkdyamkzfI2F45F2euRUo+52wf88+Nn\nvDV+DXDYj498JKw+WCDae1LEibXqZ3lRjP54icTARSFrbBAamiVEJzJUikpV\n2P/+5H9p0/npwtGZTFKrH+TcsgDFGUUtg3dsLq2DnPF3g/X5u7A15hdgOgwo\nXsRuo4kCYXoYdoi7o+E4TjwFYazizERUBbcW/52ajISpiBOxFTBlzc5aJh8u\n7RG1Y93JVEHB8GmaR+YByQVQZJYiXiZzHAdVUEGavgBGWbbEceqBxDDZs3Qv\nPKZfpzbnLE5jGCvDYCWlOGjm9VDOrVxEWEDb9pAdnDSAWr3icAYrMgpqWKk0\nriOtKmu6FRxV15xjP+DV46tpaN7paSEIKmCE94wzCxmbL4ojTE+tyAaGMJbz\neOlvzTcxEdHQqhWTTUgDs032T/yU1Cikj9AmiPBnhHFm/mrf3J8fyVf3lf2Q\nTHgQTqI+sTbQxOFuROyVrDSFU53JAESWy2Z3a2xPgkxLj46jFpjQBT04fLMj\nH0h/\r\n=EXiO\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"2fcf375cfb22882468cdbfe126d349a996b450ad","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.525989b5d.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.525989b5d.0_1573774231767_0.5436344399210227","host":"s3://npm-registry-packages"}},"5.0.0-canary.7084b403a.0":{"name":"@material/auto-init","version":"5.0.0-canary.7084b403a.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.7084b403a.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"0c5f38af54de27b056107b664fad30c7d22e0c3d","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.7084b403a.0.tgz","fileCount":14,"integrity":"sha512-i1Cva/Zm1F/8ZRTk1Kriq8H8UdHJwqsww48vg/gPVXXi09GcuweuhQPmez9jNb/2vIA87iVNh8ltglqmCnzKMQ==","signatures":[{"sig":"MEUCICePRkR/qJM4y5sV3j5YUckxSqmrR1UPzrOaNhz3EUcvAiEAuRSCNcHyUMPMp1Dq7nfQI4C8fx7HbMqpLggBqbbwQYw=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdzfniCRA9TVsSAnZWagAAfRQQAIdUJx3v9FKcMIx59gks\nQBC4B5P8LS4WQxoeZm8o1uYycJjPJRAd5uQ9qdVd2Xr1g4XKmwlJLt/DDn4h\nfYTZC6HZHboO8S6qv5/vlOID9/mTr2oPlv7W8M9ydMyaQyL1a+lFnokzaqaY\nNfctAHFMScEWfzoMRZh2BREWoKm0gFJJukbfTbB9JJUKlKbnwF89hZ67KP1W\nuTxskT5ITQ86SWGUxjLDRxwLGy0SFgXI1tk61m8bV6sEQHdm60nLdPH6/TGD\nrwgNZn9a6CWL5PYV5KlBJh9qA1Bhr0wis2JO5kRjJgErlsJcaHVxYzjhbNA8\nYOd5sF36NXBTSEJpnVBIdDBeepJk23MxlVbG978HaVwCG4c/eq+6WYjU3QEQ\nDNw3/kbxO8Z/VvuAzSqu6/uffe8i0rigg2MQ8kL7NmS2XD0iX0TdyRSbbpEt\n94F1EWczWzyCE8x9wx4430BCuwJeMbbtBdjYdCHce2XPVZf3AW6g550w5p4G\n3UyExk8/NGkoI1fCDi2Hib2w8mKpEo7c6u7NnwxLtbpagrGkpI9+nTE5GBmH\noW58CxlSuJ9QyhKrI5gocdz7sVLFH6sjLjhW2d12tFE71NwEhKm/x2poV1cO\nWq8dNBRXBgdnkseCF6mxbs6Qj/SDvUgBU0HumJtogz2AbZzEPYdiNYljB4y/\ndHBd\r\n=d2mv\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"6a82bd7664073498cf25876314019948f3295c87","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.7084b403a.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.7084b403a.0_1573779937685_0.2679143702403999","host":"s3://npm-registry-packages"}},"5.0.0-canary.3cbee6dac.0":{"name":"@material/auto-init","version":"5.0.0-canary.3cbee6dac.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.3cbee6dac.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"abf0a63f92b73e1c08bfcc3ca71ca213c69d4474","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.3cbee6dac.0.tgz","fileCount":14,"integrity":"sha512-926A5RmVQUyvlwvzUlQ7SuQnOIrmx9qWDvwTP1eg0Qv+29LvR2AiZMEJYUlHekmY2CjtPZJZlUB8K6CUpy58zg==","signatures":[{"sig":"MEUCIFzkcTsVt/siwRe+0C+JRpaiSwkC6tHlt9w8EZmuWBweAiEAuZHMZp8st0hZztSg26tNuXixbOKkncujo+/auoQPmkY=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdzyd+CRA9TVsSAnZWagAAaiEP/RV9osIRnuPaS8I8vr/7\npbhsILh9USkTap7csHZWm3EG6ZcnK/qNt66ev6z5nk8SgyaWjDZUkBpld6jH\nbfVmrxfp+zaN26JSttORKHace8toEdSAStAiKiRH9oghjlybF8LHKzSvOz0Z\nZ5eUZmGFhRfJI3I54VIXsxAcqJmrFda9IQFX7Brw2IoyzMjAZzG3/01N9kjx\ncjYkeWN9sUKWLyJi9nG0uI4P1jvSLKYWRbGDxiHzXGJjACLORhuCdwCpEoID\nw+oVsNwESnh4KSbQOnstYDZPe/SZ7rhWRwhPMr3Goxa2K7lAeirZjoEVnrUw\nmdzfLSxuKROHS6l2nwDJqxcR74IytkrXtpK+kPmuL7SgVtiPG7hYVfNQoNgO\nFGId2+rsnQz9JOxEDoti5gUWTwmZFBqG2HeQ7NQW73CkbZYMLIdvEQWyFpd5\nRe6xE7i7c32NtYxn9KTAbSvRe7xa0vDZQBjD5gdqC15A0YdIaof0FkfPBdBZ\nrs/SLSzM1bpB9MPTNXa7DHoxCMJA8mKU3LvOEUgzQqUe7RjjEaLdlUYo/4ZX\nNN+GzfpzDcAUDZ0WtQsPCAAYNgnn+GQI6L1LqqLkOpSp9Ew5CHoiOlfqjc2b\n3/NGupmGmkH0wG86tf63u9aowGl962hP+1enrndHEJjsQzvbMsELt/GkpqNA\n+7Hu\r\n=Wq6k\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"5ae37026c572ffe6707702e535533859ddc81a48","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.3cbee6dac.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.3cbee6dac.0_1573857149650_0.6714339898343402","host":"s3://npm-registry-packages"}},"5.0.0-canary.591a6ad44.0":{"name":"@material/auto-init","version":"5.0.0-canary.591a6ad44.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.591a6ad44.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"2146e9d7b43fd277aab74dfa9c8aa6145a34ead3","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.591a6ad44.0.tgz","fileCount":14,"integrity":"sha512-2mqhOA5rI/ldIhSIRn930vukVRiGNqIqb9afqgIo7z2GN6ziIOHNy2H5209XRiYLRa3TitniPdjWfnRWrNF+9Q==","signatures":[{"sig":"MEQCIApXskL/L9ptQ/fQ0zaaS3KyHXk3FuvCa41cw8+bobP2AiA9zw1gCGoL0e4hIiU/PjZIoMQJ5YVYi2eqhEIyTvRD3Q==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd0y28CRA9TVsSAnZWagAA02wP/3vWvwKUjrsNmA0NKcnH\nPL9DRbn/4o1kq+B94IQrEeKG5ym9GCLskZroYt5qA0haqHcdshqsmde9WL1r\nQE3DEjtRUnuNVKOPSVQiMG0kO0eiZpid9AmeysF+o5Xo8+A4ix/jg9cT+C/h\n2ujkWvlv5kOs2R+lKYwGbpvKRkQOSMjvj9NckxMt6paiByaaXw9WLsG5uA5W\ntEDFgTam7x20PioC06513pzaLYVwvKLAKIGp1nXTAdfP27nVmK7EGa8K3K5D\nLbcOCwO/18DU2+WRfIChWhhKtVYpSXfZEmr3GigztpqAg6kw42tllN64vLiP\nsdOTm/RhBlz9biu1lzgrdMHf7rzl9bBJJ6VQQwuPs3v62iK8cw0ldTMPLSQY\nWhLzGn/J9DwZoBIw8U7/44lItbGsoCy5Tyn+Bfz4BjhLoYAD3UmXCLzjUCfW\nTAw/ppo87lBGUzucnlIi9tDjqlSul7jDIFe9jdriHlryBUGHqRsQ9wg+kUk5\nKTpHaFZ5PwKTnR0AmjmXJrBoD6uQd5HOF6fl+9UXn8chNRHQQZnLSGtvRjmL\nWwWw3Ox3fY2l4XFs3zUcMTG/DmFi7PpHVXAPxy2cw6jRAKT9x/paCm/GLQr3\nPlamhAhFOtA8mMqV0TBeUU8O/5P3YbnQqWEADNetpYcj1h/TnoQbpwwotX80\n3kNJ\r\n=+ID3\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"b5469bc1cbdcbb7c9926006be2d2a65c3211c220","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.591a6ad44.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.591a6ad44.0_1574120891975_0.07240618487165662","host":"s3://npm-registry-packages"}},"5.0.0-canary.5729943ba.0":{"name":"@material/auto-init","version":"5.0.0-canary.5729943ba.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.5729943ba.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"1c6622df8a643320a18c6515a4b3369e37db84b8","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.5729943ba.0.tgz","fileCount":14,"integrity":"sha512-6dIA8sYAwpwWe/rTe4Jo1Q2U5ym0sBg0SpWzZsxfcY3U1MFSeQGYkkJXrOVSJyxLbSM7lSvcvFcEJsjssBkAxQ==","signatures":[{"sig":"MEYCIQCcpnxwuwMTyts0Cb8Ln1LQglzYQtuzxixztZmgmLxB2AIhAIsCBiLy8WvE/ML6hnvYB54E1wxjiiSNFWcJRDWZdhP4","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd1MzHCRA9TVsSAnZWagAA3WUQAIgUUaQ2+aWnChQdqmzG\nd2XO3lZCX4WYMkP2/uk0BAnQvU9FoBY99bZhyFjY6lEJiXAD6txtzylS2881\nr6WMA8qlQTQh1mVvn5iz+7BI2UEkhTzpJnuPpiTiouASAoIIXVa812aTmFBh\nr4TmmuEIIKXWcrIne79LWIcyFb8mHqGOvOdDX5sr2Gm0KGMqxwsrK4UxiWaE\nPL5mJLzLM/GRD3JVlM3/mGnu1kk2JtXwyLyOVyxykSx/3hv31hl32mqp7YgZ\nUGn6Y1M/cb71UkaT0t7WrCE/WdOh3DyMWygYdjnT7T0IiK9UkcAN0PyvhCFf\nZH5JU+8afBpyk3ugwTVYNw1WRw5gLVvlenUrxzoBYId/JDfy1JvqgFAhh5zb\n+dpE6qc+FnED00GhaCPwFdpj7mE5LPB5h/mXj/ofIvBiPNyDyIkKGF9HWdUD\nt/F9up1ERL1ztU41oEY9dp+beT5fiq3yGwTvLe14ZZI9vx8YdNt3TwNezZDd\nhcwFSU1uROypDyaKoB+hose8JHr/JnZTVJfBilUdcJMd7L/of4COldx0n7P9\n8uWxExNlSbHk4SP/eLgyiHBdPcLhljXOA+gz5kQjUrBLS6scW1ej8qXpqBQ5\nmuRZinudmYciCJvjG+KSRuUIWaGrrNyow1BH8lY5UrpRmgmzYRGEYEaLvJVQ\nE27V\r\n=mrJz\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"d49cf0658a3964963bb2b39b2e3a010615c815fe","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.5729943ba.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.5729943ba.0_1574227143150_0.5196725613301565","host":"s3://npm-registry-packages"}},"5.0.0-canary.e89750dc7.0":{"name":"@material/auto-init","version":"5.0.0-canary.e89750dc7.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.e89750dc7.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"a48214753298e1a6bec4cdfc8ca541dd1872ba26","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.e89750dc7.0.tgz","fileCount":14,"integrity":"sha512-RbeTS0G/uCsJkt7uS3tlMhjPYdhcHMFstISVKwA3RRW571aTFHNQTLi3GHzOXiSE8wVop+uAI/DLdfklDrM8dw==","signatures":[{"sig":"MEYCIQCPIyspSXVvC37Aj82Ue1hAx6Im2t2oHWQATqbyglshugIhAJLh0LrQPyQiMrLFaubqUKKkWOQk8JHvFBtzZYFHTUHs","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd3drYCRA9TVsSAnZWagAAG1MP/3bgBJXwZfnsKl6TWQ9+\ndwbv4xYmz6opeRIcHSDfPS03VRp5P+ekj0IeNV2e8HqaCj+eqTqEm0Yl3blr\nZD1KYVLg8C9oFPjCeTN/FtXm55hQ/CgY5r7Q5hCuS2xJ0uVYAokNjGXFtE6p\nWEtVLJun6yZWi2UdkBgOPRIomoKwNKI/3daqf98WdIXTDLlgVOMnbvn7uhM+\nAqnQRobN7hLNYHB+RETw3GaAm9naYG3lBGmbEvfbf92+7js9h5syea4KjA5K\nQKzvRn5Jt44YXPY2TYlnpDBuiVHigfhc3EgIxguS0AMzakrHCC9hF4+UK4JP\nGeWinqrloGMzA90YHpI2yTT5VQWQnBUsqbw2uKXeZW+9vXIPxf7v2dfFwM7s\n0AIKyu3w3HxLmXb4ZqB8CIPOgxxIRP806KgcRP7ToCsZ5hdM3jYBGJP906aB\nj89w/SENcESzs7konYGTx/9XnqNMeLls6MtisNWKG25E41Hwqto7P8tkJQd8\nrT2C5hHHN/ttOHMTetZPjc4wXvtsZXOZ+FbAfd7eVEI06kE0eaHigKgFmTBI\nVFsieHWdnbZUw1ZNM4b+FBZQDGqKrD9e2N0tfVXIyv1N5TgzmKxXN8pdnfji\nKvwqDF/7wYQ/fV4WGBBrkh7tTkfi2DUsKTHbIbUNoV+dTeGaNTcDFlwaGHmy\naGH0\r\n=pTU/\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"2a166b3e817207f685f4b112635eeb21f5ef0789","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.e89750dc7.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.e89750dc7.0_1574820567721_0.1856447693249892","host":"s3://npm-registry-packages"}},"5.0.0-canary.3e560b33a.0":{"name":"@material/auto-init","version":"5.0.0-canary.3e560b33a.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.3e560b33a.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"d24667fb75525da7b63a725383a80c56e0e0ba28","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.3e560b33a.0.tgz","fileCount":14,"integrity":"sha512-FFbOdOvO0ciu5m1tixEbvFT2jDiJ5z9q6+l9t93gX7b2KHS3g+KgSP6+IwX4WWW1Qpyh0udibzekHN1XO7p25A==","signatures":[{"sig":"MEUCIQCRgNAP5csszPBhG++qSI6xf878Ck/aT6FCg8kjbRP4iAIgemzI77Z79XegMoJPFivyxoHnNyGU6lcNy4cm3FkBzEM=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd3dsCCRA9TVsSAnZWagAAey0P/jyUN6Uqcs4MUO0wLuAS\nmb1b+Wjpki7vOGaLWS4LoJ+oaeeaI9oXGPAOQMO0u4ilNNPyx+7rqBXsECh3\nY1yadWmnp4tXiiLS2wqlUW5Tgqayve5Id3JbnNzSOxsk7JFaek1yfjU3Kmyk\nmCvH9zm7/aLJB6xC0sYp/HyEYUqR8gGXoFonqApw9B7jxjyy6bC44oGh6gV2\nHxmlNeo/hhrP84tGIX7eQ3/2OcjJLEk8OKs+QclxLfZEwv3gZWoRMwANwxMN\nVTOXqVIRRfBoSnN4s0czN0huT5sn9apDIEiA28AXQEkEbYAhA8r8DhGC9lpD\nQonRnp/bwaX/WvVFphGCPfAUekPtq6MsD9M7ko0L4GuUKNbAqFzj/kCkLK1j\nkBUvjfBPxJQgV0itfbRGKQKkojdWsvdJXPxNDVvJ6esApStSG7s6VZNaEjmS\nAETf23xexmyRQF0y8tBcYjrXjxaHTRtk0mH25Z4bb1IhEgjJ5vGM9x9k7SaV\nVIV/UYJkpMnSdlUaWiGylojklX0tHMiiMuuucqbj01mZuqntJt/pCpxBsVns\n0APmgycuJNf1mqCho5jm+kSr65zXKpMtxTSNAwybVUDsUjkIgBjAOercuqA0\niPKTjS2RgdyMIPILd644EJq+Sm6VysC63Dn2So66Isic1q3jPx08G9slGAQG\nFJay\r\n=fNrG\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"a86efd68e1e91c0cae784ad70b0e36c13c923dba","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.3e560b33a.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.3e560b33a.0_1574820610469_0.27427806540355304","host":"s3://npm-registry-packages"}},"5.0.0-canary.7fd17ce5e.0":{"name":"@material/auto-init","version":"5.0.0-canary.7fd17ce5e.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.7fd17ce5e.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"fe16c72dd3474b7cdac50d9820e3300e2c3369e7","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.7fd17ce5e.0.tgz","fileCount":14,"integrity":"sha512-eMalycWmJrNY/2Y9UvFbRAwyYUpEVa6RUY5QJTEcvv9pSnyoOdCCikI6L/xZAJtulICpSWh6eKumLWuo+7Yxkw==","signatures":[{"sig":"MEQCIDX2H1G2OnqXynHR8dftufYzKeKUI2wnTscZTxXih72xAiAlT/nP4j2VZh47mIPpR13Q6ekPp8C27NcUG0ixtjyUUg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd3dsRCRA9TVsSAnZWagAAkfMP/RwmWqhUHZvL4JGw+0gF\nPKE66TU+ml28yCn8lnWuV5Zwl9jTbAy92RCBx86mHRsNHA8UeQyAMp5Jqftc\neJZGw6rUfdw4I5QJFEHO8HHTeKCoNDuCuqt3YJwWbeA2Rn+wv+trmEcJo9oC\nBbh/Z96VCS6SJhGTWyKx9ef9wNj5VcwbKdkQthcqHt8ZpgmfR859s4YvEIPe\nPWqaC+aEWLMCCUTT/wXzyJxJkiqZ1xpDDUmFIKWw0eHcVfu5jL/8KBwQX68n\n3NXiE+/quM/HB2E7jgJT5oEy4keu6hiBEL3qT0rc967r5FRzqxDaxLl4K+1n\nf0PHHkYRaGbXUrfvu2CfvINU7LzJ2tEManpv3XWdoLHt3n5SSEfIolVhfeuw\nsEK/o24UxeUlHY26p3MWNZwrtjH9BahDP0w6XBLWse6NTEnr+NjOc5uw8HYV\nCnYz2JtyV07sAc//EL46zkp886JTe7Sa4zgh8vzdcmHSjHx1MgUTXFJWIyis\nq8IrnPS0y/ATOgR+nkIbRATn33x4nVL79zb/b5/xaUEVCurrr1Y06gqG39oW\nolj+URbXswS1xHoRF5A40cRf4yVcNauzK3zT+WDqB/M6lJ3mQYZC/247Labr\nTHsXR7J78BWS4GAtI8KHuWkUkhwMEGxg1ATNDrBoPHI+yXKUofotVofMyDbF\nUwjo\r\n=UDG+\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"e798e5bcdab4c998c88b2bde71412b2d38dfb262","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.7fd17ce5e.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.7fd17ce5e.0_1574820624505_0.40146091334539236","host":"s3://npm-registry-packages"}},"5.0.0-canary.ec729683b.0":{"name":"@material/auto-init","version":"5.0.0-canary.ec729683b.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.ec729683b.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"782db1e3a52dc68d8ab741bf61e1013bd87057f2","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.ec729683b.0.tgz","fileCount":14,"integrity":"sha512-eh3lDyQ3e33/6aDhYu2a7prPfnTHgxMM22QUUn1L3CF1R4kI5D5tGzJzNLODnPGk0CEeFnD8Wp+NvGLJtnfNdg==","signatures":[{"sig":"MEQCIFN2p9qFs57D48azlofCGQQOTeqTrZtzun6eOB7mmQDQAiBak/HtmC5HL/2SxQlPMSmZM4u1TOInembXy+5AHmlWQA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd3pw3CRA9TVsSAnZWagAA3bgQAJuNo7po/MFSK7w/xXSj\nqRfmd0HHOtGTI8EHj7q8dzSRW2shidwNvbPh/5VKIOs96ro8oXgTJauSILFt\nq2hq/0MCm1OAHkEC1s3/9bPJG8cwIh4PMTh/PeXeR53YS9nFDN7LS7NXmP4y\nZciFe17ejREsJXFcb7RyqfqvsBlxY5fuZb85/gDKV/T/xESgs87/Vn0ELp+/\n0b3bl/S3hitsS62l/LfivBNLO0b/po73foZBpgpB1R868M+3rE9xmwV8p2WH\nS8KA+ynlsQ5Tzkxf58xNiNxZcpAPWiJfTuw7A81Rde2xbNzTO7/qNpFbs8Jd\nB8v0aP8Utbkz6kpiQPxKYTs0i025RTuOnoYrY5XMeTO5XUNhCut1DqOlYxT+\ngp9ja/ouIOS4LjZIw5w4Fq1ZSu2jfXuvbc5wEFxCRviXfzBmzQ7cf+wK0ipW\nqWOH4mCk2n20iIHtBn8yAXsu+l549ypVusX+n1HCsrCkHLISSuZGz72DG0ob\nv0gQNMjK2rm2wk2gQwvnA6tbBKhCAjRw+j8MLyej3tywL/DF8ja3Tys8d50H\n2sCSuE58N3sDjVA9ZS0NHcGIrJoB7n6dIJpOd+PFKp+sKYbkJnl23dVpop7S\nNAM7ioBDAggbEUYRFeWu7Cso7Yxave88Zdo1dwjkDZTIpHTTCoP81xKlpgCK\n+KL6\r\n=wF5d\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"919526f37cd7606c0de4cc409ed4c1ead34b60eb","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.ec729683b.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.ec729683b.0_1574870070784_0.6540581930822114","host":"s3://npm-registry-packages"}},"5.0.0-canary.b8bc4a26e.0":{"name":"@material/auto-init","version":"5.0.0-canary.b8bc4a26e.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.b8bc4a26e.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"711f5f3cca716978febee2edd113d6acd7b3d1d3","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.b8bc4a26e.0.tgz","fileCount":14,"integrity":"sha512-QlxldyKUx2sNZJdpY8W+GDzXqbJKqwhAQt37KIKaY+M9kCOjzW1e6UEPGSqquFx1UVb94BomPm6Wun9YBIk0jQ==","signatures":[{"sig":"MEUCIQC6LigaX4edGL8sapoSky4fAkiJWeHhNZp9K+jK/aG+/QIgWqvoDuN2Ilenekz2/6Q9rpploaoBgTZs/C4/5PmxGAk=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd3suMCRA9TVsSAnZWagAAT7cP/0OAlaElA+/hJdVEcXFc\na1XMcJljnm8Ir0awU+8X3p0I4sCbzDc0hrcUupqLiiHmhBx7ii48ThhMJOWO\n+4D2eL4NSZEVehMlt6xtCw3Yd8LBebvi2sd8P747M/CbWm4CeisMANsmNDq+\nIPjFDRMYwxeTGTdMrY4JPyyH6GPyGDejrKgwuhzJANKeCSd/B6+VK0KyTbmx\nsgl/vjhVkClROAsVvDqMkXNCbsmUv6CKPlBH4aBQK7df86C7bekf7YIyqb1z\nsbcA3K3G9/Nir/+NqW7zHO73P3S5gDzsQDHN/U3upJV9tptWeEKDxnXGvY3P\nswOWsfwIPkX8g6Z8DFJGLB6Qh/FJwEvhkD2AnnC8AFhGWxJdkgumxV03ZOSj\ndofxXUXAC7U2cZTa5z8A0+3Bk7f32nH9YePkI6dzJnYNKM5ZGXVy4Hw97j1d\nzhCFAnvV8uh0HRGV8CcBfnT6IyJTHd2HFI+SSmENOeXEui5sCasWdFhSQp1N\nbKP1GiGAklj3HOoeFhizl+cqkaEkVs3RgbXtJFHzZgNNB2jmvcSMSdPPmUfk\nSTc32A85TY5KllVHj7jowGCJEUjX06rPI14Ou3V7KClloq0AKP1+yxssw3I9\n7GojW1Uy2Mgen5h66gRtGGJ+fupezPK2Gv7FnHhvwvrHj74HHglEXXNTHgsl\nTIeQ\r\n=zQgI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"d04615df572bbbf2ab2eeb76ea45696d0a40563c","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.b8bc4a26e.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.b8bc4a26e.0_1574882187997_0.2602869205991476","host":"s3://npm-registry-packages"}},"5.0.0-canary.f978109c3.0":{"name":"@material/auto-init","version":"5.0.0-canary.f978109c3.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.f978109c3.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"f08bbe13303c8b4e1a6ee4224bdd3b1cf4a7b634","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.f978109c3.0.tgz","fileCount":14,"integrity":"sha512-aIKc+0uN7df+ijLxMplaJ2OqQcBlJ/TJNeEWRB6XMT70yysui9MjeJw+1tZiugWc/QJIPH+O+aiRHXVrbCyTYQ==","signatures":[{"sig":"MEUCIHPCqqw3D5MH5OytqqN3qqd5KqYTdpyDJUHiKefW89vwAiEA5yatX6Zd4lYLNFSL/HmxdlNNBMBAPZS49vgN1gxn+vI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd5US4CRA9TVsSAnZWagAA9jgP/2xXwEnae0ugLbhgtFza\nymZmm309cJ2fGIhYWIj8L/hZfwtYPGGtiuRtTDytE8vA59+mrhYSQ/yIoUks\nkVy/3uaDp9veYLggQ6uc+Mn+ZlYrJIkhPtafoHqmZBKvKXfH6iHrmvXuwzrO\n3cSKN/357tI7bN4M+USxAVDFRaYL0Z4i7J9LqmphdsoVuMgTF2E7q2QpmCko\naWNtGPJjiVEAYJz3lNbcbyOWVvQt+SKDDcmYbZNsQGp8UEsjfmuGyXCHMJHv\ns457Jds9+hacnqszoTMSkm+oIWE1ER1MZyO5Ar97PHA0RVC1fxJzmDN0qztw\ngtB7epvLMMq1fvLWkGNQcEp/aC2gtWUCVhXvYuSAwaEcZyAUC6j8wLR6XzWf\nSvvbTYDBYQL8wRbPG5FPZ2O/V2XpJm54F5xJZItivAmd/gHv6cEO0CGhWsxu\nnbavw0fzsHoipOb0VCE6ToTNHtHXcVdkR48iABvFPdMoNBeNo7Aq7moQDsNT\n/gXIH5ArWOBTv5n/tp87VXCGQQ5kMWolCEHgNtQltqbXDMQRutHQY5F7WIoM\n3sp7Xad+QBElNWK8p8wJ7QffmyVCQKJ+xyVF28rJuJp5GSswy9U711g5LJCw\nns5YSlBVvPDcHzD7KyD7kyaS5mKMh/o3PJKTHbT85os0lI6iKAQWpt0FhJIg\nR7Kz\r\n=p8O7\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"27bb2072dd0bc0aec40da3282431f7513467bbd8","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.f978109c3.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.f978109c3.0_1575306424003_0.9835728310023386","host":"s3://npm-registry-packages"}},"5.0.0-canary.ad9dfe706.0":{"name":"@material/auto-init","version":"5.0.0-canary.ad9dfe706.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.ad9dfe706.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"053d8d8eed581906e6d4fb1c44af440866870831","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.ad9dfe706.0.tgz","fileCount":14,"integrity":"sha512-KnF1zj+MoBjVNUU4OPgYEHX284374Xqj52Veigo/KOf+GRZ5sGqESb95XgIKyOIj/WKWC4j2LpQRb8Z5zE0GeA==","signatures":[{"sig":"MEUCIHDQ7Lvlwnf9Em81Np2hIo2sMPVq/1XZsQTuUVPcJRouAiEAh++6/7UA6Wqlvy+LjETdRzfXUxXXLmvFY+scphm3J/4=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd5u0VCRA9TVsSAnZWagAA18cP/jpDLYv8vdYiV7Y+x9LE\nKSA0sSA6QhKwI+ClJ9zPyazeBNL07GVn0ksJxxPoDoLVmz5PUuy2i1D0kaSe\nR/O3k7yCvcXSPVrID2aggNayAEgCwQIy7oaj8U6AexxG1XiMz0+lAzHLnNTh\nCDiIk5mUAsc6ucnQmjpyznQ1GlmNTZwOrDRaZuZFd+7bLyxZR2b1TICkffYz\nKhUDkHZ4z0VWq4pezjlILeIoyqWpubrtq3+M0g5A0Gc7WuiZu7T5F1HGXjM8\nIR6pFI8/nlhELLGzfyr1n4QDhYiFxxmOWQcryA2vmPG8y/ma16sOF6cBlKNn\nltajBl3MtXv5OcIbeAx6r7Wwp9aez11NTSKuTs2+aC0AKQkNiOule1Wp63gV\nEvTEiwFXZafkH5gVDWFskGgN2orHQXt3wMHaQIrBjF55FCTjq2vuO25wM85C\nCMVPRAlpuNJ9pn98nSz8Cqfr3RVlKvLl20iCJjnkH1bp92z39uMCZ5NhlX1S\ntjIMtpKgK9UIyJBX73XyHRbCZymqFU95OIV1Y82I2OP1XUpP3nQWsDjsZ791\nwiKZH8V3Uk2P2ke17sfQWEMufDygQGy6+tLPXb5TkL0TYRIiGDTW9/FheN/r\nBoo0dFsW3/UcCV/LWj9FBcu14MOQ6HXFHIJrk9Wp538Z5E9HKhgwCU308qfZ\nsT3u\r\n=Oo5U\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"ded1665c7a532bca8466d5bc100026f56ea99715","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.ad9dfe706.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.ad9dfe706.0_1575415061014_0.7729059899069199","host":"s3://npm-registry-packages"}},"5.0.0-canary.5e45d77f3.0":{"name":"@material/auto-init","version":"5.0.0-canary.5e45d77f3.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.5e45d77f3.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"323d7323fb698dbc9a5531ed8c24c3552cb6a64f","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.5e45d77f3.0.tgz","fileCount":14,"integrity":"sha512-9nez+TABFx2241oA7QSSqwpa9dF2pG1WVg5PkH57xNclAwNzBb5wyAT93d3ShxyPUmormWH0Qzcv6ZOx3DnZEw==","signatures":[{"sig":"MEQCIAGNUE5dXPrgY1Ifk+SCyCBiSDB4fv977oz0i0/XjWhSAiBflKxa6TgkgL+VJERwXYK88y/yLl3Zty2973qLLqgTxA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd5u1aCRA9TVsSAnZWagAAETIQAIypQ4a4Dvgu9O5seyMs\nIc/kfkOImZ6y86mfnPWqkafsrPPxA+hu3PA1T9EfIRiwqzB3SyaTZLF0IKdL\n6uHa57I0zkFSBS2I2sQ9GUUW6tgGnDug20RCD+ewzJh5Kmg8ExrHpSUjKn69\n76vGO1Yh+3RNpNg5gUWxkQdPMFCzqhtFzfVP9qGKT6qUuZcjkQMB7PgdpS79\nELHDbDk81q8NTAxXlBpo8b0k8WpDzFPHQx65u5vfb+osqWRrDfJSKi1Ic7uM\nokBzhDuzsfTbjLzjNd3Nh03ohe53wwNUBiTOxqXf8pfnNpNW8Kf59L6mqIZm\nqEjbzESEQ7f5y7N+6665qLV8DbFNoLzY3w5iJRkjQQojNrRNQLSRqOcmM6qO\nFIrRJSDXQZOBWaOyrtopbOBu+XieiUZHRUYeHFDFoL6mazZP86+1UinKk7x2\nvyrZ1HwqA4KrB+lrzuL6sGOSeGupCeUn9WOV2SK2FZfW1VUo0PxPKo9U9GGg\n+wEC0JyAL8dlUvlMkupwWtisBHDG5DSldLZnxHGu0qcA7+r2iPMB0KpZ4qEA\nZZIoRwDR3iIH2UW57qp3yksYzEoLaJlreQ1NzXoOpCq/xJns60EqAbvrycMG\nmlcQKc+ntLhIwW1w+5xqD14asU07LkxlQ082I+OO6y1wYHz/4WyaM7paGqsx\nW2An\r\n=iJny\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"d7a20a5fb792fe297fffc09187b6dd3859babcd2","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.5e45d77f3.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.5e45d77f3.0_1575415130232_0.9028200546386951","host":"s3://npm-registry-packages"}},"5.0.0-canary.d10e8cdf3.0":{"name":"@material/auto-init","version":"5.0.0-canary.d10e8cdf3.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.d10e8cdf3.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"7cd00233ac4819ee9984f0d1283c9cc0abb25404","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.d10e8cdf3.0.tgz","fileCount":14,"integrity":"sha512-HkT+LbbVw3vBNliUi0AqjpjIcOeLmQkc8/HefkCfCHJvj1GB58ow6T8BAK4aQneqW5BxVbZ5MT/IqSJDWSMLMQ==","signatures":[{"sig":"MEYCIQChuU0fYpFZ+BxBVAMGlRy6N3KvFNg0VHfXsw3w4XsqEQIhAKcEaV2zUq5QmsqDK8GTH0Tjo5VG7C+s/Gu4on1G1nZk","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd5u2QCRA9TVsSAnZWagAAWp8P/3NjslpHki/2wjks+zVy\nrmYbu/LqXWOn66n9OiK12JgpXz9rCaoNuycwAgiyb6uJxv1SHikTDj2z8sTD\nx+Mvp800/1+aGA9mVjZGpSIYB0rMsi2yu9DXaaPM5GBdWhS8hEHkQnyTuCUl\n/YVXbnhH7Xw5XKK4YxWKb1QdJRMsfwfvv97n0qAPQ6FbhWUcL41SLbeEYMxS\ndEAK8ZNi3NJVZluxjwBPBbY3SCGjeGdbvEPiNk3qjjFjiPNabPp1KCR2dOGo\nIDo4jRbLOP5DYDu4RbhcY5T+Ityk940/s1yiItRECGgW8Qbu3cNMD9iFUcp3\nThuaYagAMxMnaUV4kEMt3edQjeQKuNQfQnsunjk+KnVt7ONjQKOLP4yK0sUg\ne0Y8wwngDmnfokWBC81ZYKqZ8t49UHfvrXgQMh87VBZccPK1lydp+VDsVz6n\naA5nPrStY8DRsSUERmaYAsTlEeVZk+/mh/2gJViHBK8r4V76qySjrkWjQIee\nb7eYZu/jsIXQGqCTWxwYaCuSz3wXhVeGGcCS/T5DU5csazP5o8C/JcI5FIik\nGFNDibPQwWAzORN3goEyf0J+tUjXvpgNLepU/quk96ibN4Y0iJbo2hS56i9l\nBhAUDkGcMDz0ZwWCZHiPG0JQw3yVhEbUHRA7az9fO3/hH3LsS6XZgxH7Kc6s\ncvTa\r\n=7+nr\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"855cf0e11682e4f0f44f50292556ce39ae2824a3","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.d10e8cdf3.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.d10e8cdf3.0_1575415183700_0.6813727197939399","host":"s3://npm-registry-packages"}},"5.0.0-canary.a5dbd8a2a.0":{"name":"@material/auto-init","version":"5.0.0-canary.a5dbd8a2a.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.a5dbd8a2a.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"8964ed68ecf1971e3cb91a83e4c86de50a3f7467","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.a5dbd8a2a.0.tgz","fileCount":14,"integrity":"sha512-WyRkhpliYTbSlbzpe4ddVhurPbqa3gj2VGPgGqQk2HOLCGTRfJC7de0/6X/FmamZB+K3wu72XNMIWwgzq77dTw==","signatures":[{"sig":"MEUCIAOW+3h1rE1lQLYpyKOwzmLxxN7Cv+D7qRpB/CeqI+PWAiEAuopG1dE4xGb1q+/LD80mg71prLpJlqoYZFSvfHwGWI0=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd5vW/CRA9TVsSAnZWagAA/bAP/27tMsoy2ogKUDgzRJZb\nZtLexKvCPKzTqXtqzLCSCZ+IsIXXEb59hrFhuuJvEUmrMipYKi2mqjMfqGBY\nN6Zym2llY2H4ySOrUfxJa87W08EttSgfAr+WF7bhit4XjyEfQEIChYgIGWm5\nk7nsnB0CLg1ruGlAfookke2+MEgzaP17Fw39CrGTlVLFyaxZG38LtC9Hub8u\nMQrEDEkuPikR3fEbnaN1ofBuMs7rl7aDLDawgZLZvzEyAVQWQDdJYDDPz6Ef\nbzVGfcdrqGdVaW/DFsrc0t3SWTdVXbk6R84FErsm4TKpVvuwKujBM76y6WkL\nwcnDv4oa/EUwwnOla/CMhUpvgscIeW2k5p2b3NyzvtexIAYli1JsSDOYXBB1\nEsmg1IY1lRUcs6ya0QK4KgmeuQHU0ulcz71u40wSIcG9qD8sbBhF4J19f2nj\nMdetgYJrw1JwLNl3I/2aDKeIBgvQ9ut4lWV15Siwk3QIGOCiRYCSOjGBS6xz\neRGgtM35RAxzSKVJun8mdbLYWfNmd32dOi3TFBoSL9sHBlp7I1KVjX+1lVSz\nOTGPiVhrLdUcDTWzssvjJBaV+Tqc7iEmJLj0/mh5UL7B03/QsEJ5ATRg0yPV\ngiRfi5LLXxQHoIx8RBBiHC2GhmgEw/pKVXKuOZq/wUtshtrX1ahooAO9EsbE\nKJ7b\r\n=4Rfn\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"8a67c95c393a733414be4fc008baf7637a9509b2","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.a5dbd8a2a.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.a5dbd8a2a.0_1575417279612_0.9338051452022598","host":"s3://npm-registry-packages"}},"5.0.0-canary.ba879b68b.0":{"name":"@material/auto-init","version":"5.0.0-canary.ba879b68b.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.ba879b68b.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"8ddc8d2fac7e6df69495686130891565c3dc6686","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.ba879b68b.0.tgz","fileCount":14,"integrity":"sha512-e9hQC0OGN0qYVNQGA7U3QwufHsqJVBR+i4iYJqwpX0chVdOQ0Jw2ATVgyKwkhMmll1Vy2uc6c9VscXrn7dZ2mQ==","signatures":[{"sig":"MEQCIEKIjn2b26YSAY5ONFNToob9N2gbgqd3O5fJGrT8MjGZAiALecQltT4518KJR1/Fr+Zp/MTGOto/gpCeiwTdzy7zdg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd6BV9CRA9TVsSAnZWagAAKV8QAKAWMNIkDgsHdkpx1kjP\nzpN+r/OJ0bshN2eFQZ2NsNVoeTMdkuSBD3sa0VBebLP7t3bhg47rqv9qFUM0\nm/8A9OlXYPl4Mlqrp9Pjd+OZ2/nGYds+QQbFNK5nnZ/XepYsmMjCj+7tvPR2\nUsfuMWBdmcRSBtYKjFxEy9V4ipBhQFovd+AG7MJAFqqNAD5DcxUiOAlX9FFk\nhvKZHBcpzlCrOCnOaK2TsZh+ar4KPyFyCyMg1WAbhlmFTQQqtsOrh0MZTjm5\nNCm8DNsvzouU7HzZ2JBy3cxaE2/zO+WGfTmXxuY5JydwtoU246H1dxf8klqo\nXshl65dZcuHCIXr3uVebl4xhTv9nEKA03s4PtgbRtpkUqTWjryRkOi8O8xFO\nz3oBMxuNiSZLi/Lzk6zOralVpUmAxi/4icXtK4BipIiZCfa3naxURLjB5jPQ\nH7/mp+A0hcKf3ucu5a3W2WlxL75cREKLt9D88AQD0DoBcmfQnk37zz/pzbLs\nS3v7Og1mOo1jTqbKkBHENZWoMKUrtSnFYdD6hmAs98GsPqDyKpsCPWgCT71s\nmj+NPSX+JF1sgwq2KyPsCoJ3sEClkfxWzHxpBxmX0sjua91uS4NdzpZ7+gDx\nfsnVNR0Ckpl+SqUneJOD+aYaGRSrzWBYw9xCCs5uYCJIigqAIPTmEptrNHWQ\nhdso\r\n=h0t/\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"83bad042ea5d5cc8b93df88a1d4730099550bc6d","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.ba879b68b.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.ba879b68b.0_1575490941383_0.3656328116642322","host":"s3://npm-registry-packages"}},"5.0.0-canary.aa0eba489.0":{"name":"@material/auto-init","version":"5.0.0-canary.aa0eba489.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.aa0eba489.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"98ef6bbcb72adbfb4d73f15b448e1c66458cd7f3","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.aa0eba489.0.tgz","fileCount":14,"integrity":"sha512-qCCYOW/BV0L/PsOakV/pNrHAQrjDgc8cQM3RmMLr14Tqe9QStJy7FoQ2RBvYvHSKoOanZSUa3Ou6R9eQCGT+mg==","signatures":[{"sig":"MEUCIBMJGoVTnNZ96e6GSEV3C+lJq9xxmETEy9jP0Yj1Po2+AiEA3LMmnP4XHGkvAdsQvxzIYpI6oVIu3hXymqa4HKf44vg=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd6bXaCRA9TVsSAnZWagAAA04P/jvG6gjrgCFf+EtS3JRL\npqmlsrr+hC71fcmUCkQj9b5pRfshDiXYqy1AFLfAzMEFbFcCNhdxLxXPGrJD\nNzQYCXrv2jcEP2giHCU9tBjuus2XQOxxubNb9EemdRouyPFn8N27MvhrRSHY\npxcuh1F5mxP2WZeQBtcEk5TJfEEKCtgli5hABjA7hy2nTELJ2MnuIfWObBpX\n/o+DjyWIXpnS5XKupbyLf8Pf040G2tNqLQV8TPYVEqEF5rmSzpchNzEuxP1A\nvoG29Rge1PNpnJbfS4Sj7ZfSdSPpu+lVAD/17oF+K0j1GVlQMLapOW6vDNhG\nECTaOH8Rw8ynbhsbJfeXABIuFykwbkvduHxR7tB78uM5WDaWxEk9aEbl2G83\natT/Gbtp+Q7zOD2mwXDgqj7I0+q1NQkqL8N7KDMpCdaVjz9rpCDJf3F8eMMw\n61p9k2ZZJOc+MqJdShIYlr8qb6BvaqJjwytAP0uhlTtRMn4DBG6F5/YLi4mZ\nLM3ABuC4Di/NePFoW+l9RcOOsm98vr6RjR4ZGE7QnlCBsof0vbmhkvJbewIr\ny6LG7h7u/ExQjvZm1ZU7hXH7XgckU7ljGUPAkpbXfrzPoLpL6AibyVnaJhtn\n966/bC1XcgCIlqVbd6mL3Iaj4MdyBk60sjGAjOlSk9CWU65PH9dDjfbHSh3l\n2VcM\r\n=Fk84\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"50ef06854f8319df2975cafcb0b8c94fc399f155","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.aa0eba489.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.aa0eba489.0_1575597530403_0.4981271663071112","host":"s3://npm-registry-packages"}},"5.0.0-canary.cb7b71a86.0":{"name":"@material/auto-init","version":"5.0.0-canary.cb7b71a86.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.cb7b71a86.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"b822bddcd75e8932aca676f375be8838325d7302","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.cb7b71a86.0.tgz","fileCount":14,"integrity":"sha512-kFN/nCEvwJ0KZpzAgi7bKFQW9HdGXZXqtiipIZKCFIXaW3YGVGJaH0HH23lDfqQ0lPLqRvrsUoJ2AfD0Q/EWvQ==","signatures":[{"sig":"MEQCIDyVA1uOb4iHMASoDb3FdK7AXMoelWGbHltZpU10/N+TAiA3HllqY1lOnDcP1wCsAEkbRaNNex2BLqeGQFKS1x/IVw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd6up5CRA9TVsSAnZWagAABFAP/jfUWFOWgKdVGK2PuWoJ\nmwqNV4+TRheGnvh06b/qkmQyJVh5DQRSBaTIL9pkWXVCt8wN+aVdbkk1YiKg\nIsFzyIfTcm3jMm6T/AYq4YCZAj1g3bybZeLzVgGpm4nwIQqs7XouVB89HdMk\ni0U2uJydewgZPHVPp4luEcL3re4UNxYngkvY6uw8DNX2fsoG1cn/SZQSPKva\nxuYO9u8XXakNCMkee1MGj6AG0NFBuo+Q0IGoFhFwVSRgJDM1pZTkTXEHVByD\ny6gsEogK8CShiymG5e2FyRS7jU6R3xKEAqAAC7sHIG9D6UQjVZeltyySZDdL\nmG07QhARMF5sfECAUWPjUh7QWw7yEAouW8ycAKEcSY5e8dJSn93PuioqUlzF\nxEQLaukm6fOFdQcP99JZ08ExngmxjppvOU7gf7uxS54IYz5mwk9A/T3+p/r9\n5e3Z1g1G2KZIognFnKxoYxx5qjB/TEmr8LhkGpCxKac53NdHW5YPIpPWzJUA\nKoK9Rf+t8H5c8zU9/bAaeG6IsLFda+JtfnNSitSuuuiJX/Li1mPwBtnIQfea\n6WTV25jytSNIyrGPK2GN+CDeGNLw8r+4XZXz7AEmg6ao73lGnq/zKp6OwOwS\n854hc+cU6gc/ElXiXTSlfjgykO+wxjq808eDk/q/6X63yES/2a/729r6h7pD\nh9Ct\r\n=DOGE\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"2866cdc43c0ae69bc09927b490f0805ca21adfcb","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.cb7b71a86.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.cb7b71a86.0_1575676537041_0.0018362555401911784","host":"s3://npm-registry-packages"}},"5.0.0-canary.50f110a6c.0":{"name":"@material/auto-init","version":"5.0.0-canary.50f110a6c.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.50f110a6c.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"01beaffc0351483eff65915eb754ee829af940f0","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.50f110a6c.0.tgz","fileCount":14,"integrity":"sha512-9s7Iznqg1Xb80D3NG5C+WUdE3rR2Z92BcUXRnwpymgLWKhT3e0TU02fjx4dAgrt5avNRWx4/+3vmo37BUD2cRg==","signatures":[{"sig":"MEYCIQCnMezsr77y/mT3cUBRc/k6zWngAxrJ/cOqAW31qI0zugIhAM30gQPM425Jg0HragDQpEXK4y47UGhNe06vAOFSC/qv","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd787jCRA9TVsSAnZWagAA+mkP/RiiEETbA/8JDGL/MGKK\nmxwARP1rQBqrLGHO2KmsDkMLXEYkDxRMhABkemXJ9FGvzmhq8GJ9akv4s8a9\nxMgav3oaMHg+umxCXrML7RdX7VbNrHvLB/LZwePm2dK4b5+6nJwzHcSy/+4n\nIT8vwGkf8Oeg/EVOw2qrEqckgMpRrKYxQqPzGx48jdjT3jL3+wrin3YvHbe8\nQ8+zRn4uE1I7oaNU1jI5y1DaFclDNpzOgaNBUvYA7BetcrQ3mgTFxzHq0G+k\nBbMNHgXgRz8NSCuHeTDVYZgyShaFcC/llL7qyk8wc0uZQpPI/eaoB7bz2npO\nBPYDw+pAdTh88hrw5s9zvBc6/DLBuRjYvqXNjmkcUIb23Hn2NUEXEWQCYG/H\nFrYhzGPCsQ5P0pr2SZTcbE+YK0qF5H+2dsms+61NGUxaNDznjuZ64011LSfd\nxBxzNphegx1f6UeZXi0CFhcU3S9vLGA0ms1Zukwt0v/hqIs+Ifc78joXjrbD\n5jywlJCKeHkmwhW/LDYr8OqHbgn3nj9ymGVks5tLicFsla3JV4970GfABJ/A\nuH/wOeitA1173W1ZJXUJsp5oP95RFWGMiSmL2KqZiJjqA+kbOj7W5OvwutK9\nwvCVyPb20RHVK5Ik1tUsw5JzX5C33FZIFeKXOJgWf6nJaxSIoNQ3/W4JGyUI\nSsPv\r\n=Hx5f\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"84e9b8113e75730b3079c429f751cf857a866b51","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.50f110a6c.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.50f110a6c.0_1575997155473_0.45969794944243825","host":"s3://npm-registry-packages"}},"5.0.0-canary.878a08b7c.0":{"name":"@material/auto-init","version":"5.0.0-canary.878a08b7c.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.878a08b7c.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"0c394ae6a9f8e202741de312f172cd60b9025a2b","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.878a08b7c.0.tgz","fileCount":14,"integrity":"sha512-iZIpfCR6AuvVnbl2csBJtTLl4k5HGIrQL7HfBykjQViSPE4M+sp4q9j0i322EdIBXeNLAp1lUJs05DhSdGQLQw==","signatures":[{"sig":"MEQCIBJPyGKH24OUX6W5IOzil4UnlLedNUdJgy7n2dcVElZDAiAPNZCcfE983Kh3gyZocM+r+FhTRhH2x2gcsA0/q8dH3g==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd8U6ACRA9TVsSAnZWagAAixsP/RJFUt7tk+lrq0BSJWG5\nbZ5gkGVrWXp1YoLuIYCuzLM9IyIkMBdaBMzyNE13fbyKp1x5CokJVBgLbWhF\nljMMyGxriuvpT43E0VjIP6r6xFJG56ZVBWSx6zBr6T3B2+BBzAi6bIfZJCcw\n8YwEuoYklKAZeAMY+Rlq1D9m7aZws/PoSrBp0EPm2giDea0NfKrcTxkLK13+\nC8ZEUiyiU1wC0cHk4KxSKcRxHwmg5/ulKlIOqkjrPzZvIAGialYMDJHWzKHo\nM6JypHIyfN4GK4mu0eZ9x8Q53uLj3uwLat1J6xMt0OC9VrNlbvM/gEfP8IrL\nfK1XJo28yo+zhqGkaVcLIPk6YTFxuWeWAt+2jY0ITPhd3+b1PwYc3K4P4uHK\nfhUONJ4Wp5iMdKqzGt+P7VCizO/UARjKCX/ZKNbNN11P7dvXW78HvAfZ+lJ+\ni1WLD3cEchw4Xnu2jIozonK4UZnhGT2MvoUXz4aLGB+eLQzvz7HEZPiQLj+v\n7DMeSrgMjGsWYkUx/7d8jjqL8MbTLJrTxgexK5SXUmlTWvHeAY07OUby7aJW\nw8ipSK4t7R1RwC6YD/1dP+Y/n18z55qbW7chZdXReqiTrjgVgXc1BwEXwPx2\nAK4+o/VtKFGajwyeKtg0DS3X+HscwyZoNSONOgxRBbscoY25CLkofIcGhnxR\nfXTx\r\n=cV/b\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"13bdf58f09c0e231663da8e8e9856d7a442efad5","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.878a08b7c.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.878a08b7c.0_1576095359604_0.329390243232103","host":"s3://npm-registry-packages"}},"5.0.0-canary.397905b4e.0":{"name":"@material/auto-init","version":"5.0.0-canary.397905b4e.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.397905b4e.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"7a70888d0bf38e71b6502ad796392f3a97a40a51","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.397905b4e.0.tgz","fileCount":14,"integrity":"sha512-eBCbmpjNwGocP4BM2I9zU+cdqYQ/aLujdrKAGcY9aDBy/Y4DdhgwzMKn/+8sn1fDC29VM/xAiDuzRLdF6XrQdg==","signatures":[{"sig":"MEQCIBplGy+16ZKP5wGFkY7uFNGo11ZO8zCVgYvmeqkCYpx+AiBRkAIJFogR1oCx4uQ4rCqmKdgOHDdqlXTZMwAQ4SbLOA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd8aogCRA9TVsSAnZWagAAUO4P/i2yAjnoxlhPpx6E57m7\nGXRgPD3qaiuSdjyBs+3PQ35FiwdekZrDPFZdnRvFNwn4RSJ5gtzlwjmeUTIk\nC3kI+s02YUr2tfDtNl9ufyi0NbZb6FvtgOgJg8r7o++OhKzfhvRtduiiZdvB\nHEvmo6hs6am5QM95wQ8GZoS3458lH8Rcq/d5iyZeoQF7x74x++/xVww2mJNz\n751AIdju9Q/40wwvTeittnXpFAINJHnfdz/t16wfe0NopWSzPaxX7ss4igMv\nlLmdLFJiCrZWUL5rkdrrEWKRgENIQBCPI1lzwAuADIZUnE1zw6REC5bx0rDv\nILKQip5iJL5YQcJu4GHEY/qWX2zN+4SFBVMBJOw1v9q26Nx6Wp8uOvZ4IB7w\nql2pD7A6xFyohGynOTSDdwmYXl9cek/RZ/j9qjKB+M45gZHcANi3oZBJWB6I\n8xWPi+y+6YY9fCU8kvhE2FTFAJ2ibNe6+MUZIp0HmsNLRgtMZNztVoH5Gp6H\nqm3e8LS1WV3IrW3F73nYfibo0Syiw4jsNfdTne+XJrSxrBwpZv5I9ZmKwGIM\nJaDGAaOZLYQcjqSFIQrACn/2p2HTtqP0MWMtMQqOr//TPelNyrzkVcDNdPC7\ns8/QiOFF+L2fHmcajHbq8hAfq3jr0KtSGz7rbL2tBEb5NGxRAhmJ6Zl/Ox2E\nwXD8\r\n=b7BC\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"43ff8b8aaa48d3a31fc6835290f1ea1822301146","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.397905b4e.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.397905b4e.0_1576118815840_0.4006856872948772","host":"s3://npm-registry-packages"}},"5.0.0-canary.1fbf5bd1d.0":{"name":"@material/auto-init","version":"5.0.0-canary.1fbf5bd1d.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.1fbf5bd1d.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"8fe37fcc5cdeefab919ea645efd29eccbc419b48","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.1fbf5bd1d.0.tgz","fileCount":14,"integrity":"sha512-cSq6ILLZNAxNJoSAuKdZQzTxMb/wylvVsr/hh7Ja3dUgS9RXsD03wnEfNlX3P0jYU80xRB4hVzwJ7CnJYDo6gQ==","signatures":[{"sig":"MEYCIQDjSAlk+tPRdkpRgoIvyQBLCF3jzfBmaz3Q4syWUKXo4QIhAPGC60oA8cOvYYNVVulDB1sHd0gSjClnmQUA6WqZPdoj","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd8o3wCRA9TVsSAnZWagAA8HgP/jQzMXbMV26haeXDB061\nFkbe2mx2b4+2e/GjmhwBtlrT69ptBjiKuOSKf5JQZKxwnUBQuJtlSYnoYKDa\nsB60ZVCl/qQ8lCke5RyPnR7HSx+Gbz5unRzHT/OOMcAxAwW9u89piLCkwH6J\nD8uIijx+cqY5Ni5OfBVrMHg7er8UQKWbydH2WciHZf7TsOy3qTdrotLj54D8\ns+tIJVpkoLVYK6ufYd/IgZgDyp9IJsb3ytsWHH/Ux6opcbiwWMgTXmXtkROg\nsFqim77OGvX1oXAITP1nMH7398rk9DhG9Ouxb5QBLp79wChUBIvQfryNmwlT\nHW/rJJZxRWvABN0386ApMzQor+nxHU8V0ocAjgAi04uHXWJxRiMIIlhU+FJo\nKP+Ba8l0Znz66bQvZymngO123zE47KGXXM/q7mtpPBvVVVxDwTa58qvnYc4b\nsMpblOlPcfwIPblToVaoDxwGptTxMl3bWzH7rCBujBnRJXZ6PANSpxas6mzy\nRPXsgFZZen26EN+BGrlYef5XjpHARFtegPHPbq3JqYpwsGwotg1QWK8TgDRV\ndL5gHC51aRV/4QeBqIyPPE9w+r3iMS3UynIpwE2hTf7uFYB0GvHNQKVu75nh\n0tEx3dSN9lmUuUDoOjJOdzs5YTYqHSoOXFVIEPqvn1iAmeJcvj//VuJYoU40\n44Ge\r\n=Bgmz\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"d1aaf5edd2a8bfd34d05df3e3c52dec6affd6812","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.1fbf5bd1d.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.1fbf5bd1d.0_1576177136543_0.08745059499616525","host":"s3://npm-registry-packages"}},"5.0.0-canary.b723dfa78.0":{"name":"@material/auto-init","version":"5.0.0-canary.b723dfa78.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.b723dfa78.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"effbd0a2160f3ac94ffa41c773f72c79abc95d09","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.b723dfa78.0.tgz","fileCount":14,"integrity":"sha512-8aGNjclM5Rp+rJlIYjYlQXS6JLGAD7zFm8DAChuu/pIzIvohwJYjkZNEBUuw7jazeX0v6TYFXnH1FEC9vrIqsA==","signatures":[{"sig":"MEUCIQDplgvEpXOWbIPvhQZuRVRHBlctlMvTDxz6qlQ4bMv5fgIgL2U+n4hepTW+0Ty37HigzJRs5+8A48GYLbRsCkNPlLI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd8p51CRA9TVsSAnZWagAAmaEP/R3ft/kvfqU2FEa5c+Zv\nTHLYAv0YNae/nYaS1zDbyJhazJkYSzuCT8WU1vr5Wy1HzczSwCjpP/25Xiwq\nOryP+rA5sdyPr0X0CunA/SITlqihvzenZbEU4Yi6pfYuhlphL+JniNqwUzRB\nfDds3duvvYtL9YswpQ/H+CMigtpA8EjSjAYtL9rOgZojwzhMgkFOmTwjWati\nJPBxeJmrWj3FvOUIAtL6d//52Ntd4N+1B7yhthicj+VIdF0+01/5397xuzYb\nBkBC05Kbk0mtnjSiaZME/rGsRr24utOfUB5jfYkl0b/OpQud+iKVZ2Q5dIy3\n0R2THWSTJQrXs6iXeGtzC/pXJZ5wM9FXt0Ey5lxniPaY8li2UH4Qtyqoyl17\nlvQ1TcKwEbGbSPijM4pMf+i5otoMC04g7GJPHqwGm8AN/iQopuYvxtT/CABK\nDSo3fTv9/OBAnPUzjLXsQ467SI4mWkeoZivwsm+K84oanxrSTp2AfV32fW7l\n7QwR4RnTuV8zD7uigjKaemidGAPPPYjvW+R0I0Cr1Mv0Upp4cLyEwMA+kq7s\nDWBwzWmVMsLBkFfFeV5i0tj5kGxtF8ydehSU/mFPs7mjB3UJvPNUs/EbTrRD\nX8DyOfJ5Dz+Zc/LJlpVnYLOit2OiE9QgMisljdd42QJsWvkZ1+Y7EFftfFfQ\nBhUv\r\n=HV2G\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"643046d4c1ac458ec8eb1623c5951b3c9a17d2d0","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.b723dfa78.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.b723dfa78.0_1576181364811_0.6146090331463265","host":"s3://npm-registry-packages"}},"5.0.0-canary.1c494e567.0":{"name":"@material/auto-init","version":"5.0.0-canary.1c494e567.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.1c494e567.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"213f095da51286eb67684f3243bfd00748a10be5","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.1c494e567.0.tgz","fileCount":14,"integrity":"sha512-Uxszze+Va482BslPgd1numO1X7TitcPGlCfUvmxaOlG7XKsYLNj8gIZt1tgr5MCJtYoUbhsYTZd3OM64eFGcXQ==","signatures":[{"sig":"MEUCIQCN7V5wgbfNZ4EKsvaua0bhuniwbQR6L5HAAMiYaMKXhAIgfx1wg6BIyqkBjj/K4IPBZH/u6LJrtzBAGffs17q3UiQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd8s75CRA9TVsSAnZWagAASU8P/itb/NO9lLdDg8ZjrCrQ\nLwBzQd/F25KKdJR4oWjti55jn23T/X2MLly647JsoN+AKewC5IaYce6IJdyc\nPodADe9q3X4ABZiDaRKIlgxu+9uDI6udSbjtrOwFl+qrizkSmb3P04ABk3RT\nS2yi/C3MeOSO1Hy0iSH7Bvpvn1Z6EYdrtTiqjzPXt1Awbu4hdgsm0skqKfCb\n2nNTZXl2uajvagIYYpJ1MHFmRdJ2qPTyAOz9IXhcjU4nubo9yCo9/O6PQcZV\nKtuMrqRbVByQTqR6SPs6K4oXpNJMHnKVKl3x62jWpKaVwRSBNrD+CHb7qOvD\nFGTthMp1k3PeDzswFyuhabM2GlFkdejvgoEyASzr/jKPUkuuv5Z9eANKe7zi\nI/o1wVtlfzROwJvtL7nZLoI30KWOCLjrdaRLyOEp8IhjORv+BgIcxyWmAklz\nbtqWC+cqr7r3t6zxg81dW/EHOTuI2iNJXi78dLT7JZF660QXWsFlPr3p7tGz\nspOrH/78rE9Iu7TCJSHfXovC75jT+5uEqtgkZNdZtIRkt9JGds0YbV8chy12\n8SV21gzVqauS1clJ26jyjvwu7E/9l4u+f9YadNozLxydpi9MhnSMDa9kuMxo\nrLpt+6soqmVNIDwNjYPYsjCrz/HXh3CMb2dhfeYl1ORrFdcZ6tBCzndkPnBf\n5H6q\r\n=Gwti\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"d7e01eeb35d8a54be431b39b46b389f3b26262e7","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.1c494e567.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.1c494e567.0_1576193784980_0.6450582131013001","host":"s3://npm-registry-packages"}},"5.0.0-canary.c9e98a125.0":{"name":"@material/auto-init","version":"5.0.0-canary.c9e98a125.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.c9e98a125.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"c0fb5fe779e9b49b0f7fcfab2bf39bb1f9315650","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.c9e98a125.0.tgz","fileCount":14,"integrity":"sha512-f5ikGIMerlrO6g94QrcdYW+NvYIQrsGtsJd2IkQYcFuHdupzuRzLx+7YzlZ5hohx8Is3vsbgdePqt92SyTefAw==","signatures":[{"sig":"MEUCICejPyeImFRys3xol7n62BiVZVkyr0GoEgkrIRHY2nEjAiEA1I7mRxcyzC5McI62xrpArKGh1KP8mayOG3yfuzfcoJI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+RnTCRA9TVsSAnZWagAAr6oP/1fI5yWj6QPgTuGaXr8m\n7DKR09Ku8Q4fW7w9pTIwoLt2XbRp6njKWmxOWy28jqVduiy5m6WHq/5ctTZx\nQea4OS6x4VFauuySKY7KrOnyJuePGPaPtdnvRvhX0q9evvDk+YPPCNl1oCNs\n3yOKQ4rqLRfCcE6hRN6KksR65KEpaU2xYNARrwgjzuL7+ElaaWKG2sY1THla\n57FXAbFHPZ3cw4DinsHCC7d0T1Ba6DXBgQfNfoLt8AvZ7UUUlV0JRm75JlJL\nI+Ek0Y2OvUlzoN9uL/NysA/b6auQrdSagwJ1ZqroN/fMkGOiefUKRSxiscAR\n5+OKI8wtxMeIzYf5q4ccrp5HivBEiKDmsrCoNa0mlhtR6/MAqW4mKGF2Z0eS\n+2dC7AZgrt8uFB0a98zmJU7RkpVEQQMr6FJXJAk5PRSu6tKHRYU3t9eM4+zR\nF5RZswqmtf240uJf0h55v8J/YQFGrQHTZVbhV0AMMUzzvBRX1IgWwsXyBsaX\nttj+28sRTlLlPSLmOfwXitsCrQrzFHO9NJkCONSiUp8mgtrtInN3Jo8ts4xE\nym4bbSojjBg+te2xI6LAB/uPOwkV0RrCFDT5dmdypY2nPLWIO7MFhjWCPCes\n/1DpPjXROqp7bPZsARIPKQF+WZfK326242/vFD7dJ5cDTh5yo0TaNv77s+Pf\nh8Jl\r\n=ELlf\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"34b4d9d0fdd6b65308344880ca9abcb67a41ec58","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.17.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.17.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.c9e98a125.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.c9e98a125.0_1576606163150_0.25738101491713916","host":"s3://npm-registry-packages"}},"5.0.0-canary.5ffe8f7e3.0":{"name":"@material/auto-init","version":"5.0.0-canary.5ffe8f7e3.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.5ffe8f7e3.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"49cce0f1dc9dc3cf5dfb2b5c6a8d033b7ae841b8","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.5ffe8f7e3.0.tgz","fileCount":14,"integrity":"sha512-v4t1pOqQ+K1Crw76htOMiDUDWh2sBrQZE0/HW/sOhgDRjrKJKX1JTxCCx38Ib4qdKJNSTgig6JMe04qe8ZHtRg==","signatures":[{"sig":"MEYCIQDYGEp0/UdvXfkiXlkJja6qG8urm3HQtZU2NiYq67PxgAIhAN7cHLq0BejL+LbEtdlM7Uf2D9LzzIR0W7fYizG/iZ/8","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+VebCRA9TVsSAnZWagAAwp8P/jYmqGo/G76dahoGtbAQ\nNTrxFcZ21ErELvU43LOD4QsjwvsdrCLxzjiz8cEBrcW0NzkmvDlRCvF4UhxY\n4vuwrjmIf+diI9HAsmW717+VmLiUzU6tvdBFqfHcAaJ8EzcYbrUavtCRB/CQ\n0zA+YJUmVw8PTZGfC1KwpCR4cBcGKAUKPizxMaQpS1FFjLM+ZF26hJ+5/4V1\nKKZDUwEJwNRVvDOFlaIe4LfjGUvd4oslYlRAFiJPIK1sVyVrVAskCQn5TMXh\nyVr6cz+ECCm3mWCuD171ljjRxqTS3s33PoKV3qiEKdXoG0HdE4yxRz4uPtA3\nxEoRrBYMwSU+6uKa3GUSVX+GCA5jAynrMMllxDoW4MJM4HERh7Ny3t/ynwHo\nDjWnbLUsbSG8dSV9YDKZfTN2DKy4hTV+/K+p8GWVxtP0smCLDufepuKV7Oc8\nTE+C4S0aushORVBOZ2yqvXd0QRL7zmOmNgBe4LFT0bNTfAFcQHQIs7Nrioj3\nYyErOgYLJA9HiGgkRk1t7HZ6eEnrRchdmRfIajbSqqvcojD/NK/fN0TKEfsc\nLSd9zeGvuyXjY+ueelHAlNkCyBbD8+zb0shomHgjfmDe6dDGmDewOuq57Iyj\nnbaTSZS4EXwImeL2EnNCo7PhP1uJo+AbKjJpPCUZhEH4yK3rv06rnZ92WbBw\nIsQ/\r\n=kAqK\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"21e7c11057bb3bfef94ff10e24676b9da6f427b4","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.5ffe8f7e3.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.5ffe8f7e3.0_1576621979098_0.2748631771478145","host":"s3://npm-registry-packages"}},"5.0.0-canary.47949b08e.0":{"name":"@material/auto-init","version":"5.0.0-canary.47949b08e.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.47949b08e.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"6685ecd1db5e609ebb2618e5efc6acaf2a26de5e","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.47949b08e.0.tgz","fileCount":14,"integrity":"sha512-GLcxFE41svCE2v0An0MdKGoCaL1/T8y4wIZnxJReEVJcmJRblujTaa9/Weq+F45KrQXspHS41EzoJrAwr1BaSA==","signatures":[{"sig":"MEQCIHSQTOtOitxtTzSU/Uv9KwnjB/QIHUHiLuM0kH81YrmbAiAtJ7RBVXAjmLHPP+E0SFnE+CvYri/M4ReTp21N3p5TWw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+mR+CRA9TVsSAnZWagAAoNQP/1thaBSqVYCK1M7OLr6N\ngtrmqF/25PLYLW6Y5PRlQ32YMtwljP13DVV8rVHse0/4tcEbFnosdSaBoK8K\nQcxV3H/3RcGaic9z+8LvU5RDVo6UIIKt7M71bTQD9yppfJe7x3n5CT0Sj7WT\neU7g6yKjufWQ+9DU2fS3ATN4wnWfLwBoOJZtDCivCCY1WYrI89qC99Q+peCF\nAtpcWk/x0HrEYwPwgIwsRoewnYOibaW4p5tyQn0R5PsJcRoj1faSd1XFNVaJ\nPA6OYf7qZap1FLQDOzNpFfbVzlBeW53NP/n2n74a+lSpLTPQvEbx5WiTgyxJ\nzphGSbcyRlVBuzMhM/xbEkUv74I0aiYUoyjdUw/JUb4Bs8TmtOuTu33fH3qv\n1BtWgrMuaLGV/E/1c0nLYkVeIWSogfrvSynqSlQnjaL+wGxmGLLv6DmZriao\nIGeqZOZdP4JsJh2mXLx/sMb9BrPk3h6r1GG47Q6P+/NsrLiT2g5qIrXXilC8\n3KemuGTlvi6ov7CEzWGbb4gPypdhtuD8hUm9vHavNdvjwR6K5b/m/K+RVcKg\nehFcXaA9qJ2i1wTicFHQmw+Znw5cPWNYHDSeaGKuc4+HPbUY+0OjqgBW8Pzz\n1uNHQ3U6uLFmEB9p07wzNTT2S9Uf2mQTCPdhltuWxlRvKtjcNiqxPJzufgsM\n4IiI\r\n=h7Uh\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"dc8ea470b79b9134800af9e8866b99949c575024","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.47949b08e.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.47949b08e.0_1576690814557_0.2646442607531414","host":"s3://npm-registry-packages"}},"5.0.0-canary.b240bcc1b.0":{"name":"@material/auto-init","version":"5.0.0-canary.b240bcc1b.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.b240bcc1b.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"09685e498abd65fa872580351dc04e164e755f19","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.b240bcc1b.0.tgz","fileCount":14,"integrity":"sha512-yCpKgYDWsgAJQ8Ngq7Os2qgHq66dEAc6Srpqwhri7cP2RP9B4V2d5dzXUqTqC7hIQUbVPwuX9TnwJ+ZEkUfVLg==","signatures":[{"sig":"MEYCIQCfTaXdN8MW0jWH0RiIWCynFn2PuZcLIPUkoH3jgilbxAIhAN1vQ5SCBBueNMxIvb/d935Ro8MG3+8fxN7zLLGV7zQZ","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+nsHCRA9TVsSAnZWagAAZnsQAKN+EBmgEoVRYzA/kcGn\n45wiXZlxl/SBJed1BbZuyVU+qjnYrPFSK3JzGbTprf8oEjw87xMLzYrC6rKS\nEzb6n2ipih2cMgODdsQY7Ysj2d+v0IVyUYn68AElhf7tdcFhUvZubqgI6+sH\ncO+xgqjzPWIKH0ljm7H8C8GPk9bUd1BW1wjE58JBeRHKxXfZzF6eDK4kMO7p\nwqKA/b/y0O19quk6ODL6fzypKREGLWiAy+NzKLnSi5uQtnmn7GtKGT5Ib3nQ\nC0CtzStrXlURDL4ut2p1Zm9kuzEhjcOTf55hJQryNwKc683wOFcxQnYGF9qI\nj/zOd6haPzXE/Kgg3AU3xjuJ0RFKXPgE6xoTwMYBEX8rvcZGVvsYuPjx2iiF\nYm1McBxNTMpTYYAQ91ShkXWrWdR3+sZoE0SwDDYQ/knTpVJPTQznRx0s7Hox\ngYxPcEDysTthwf5LNLVdPKHGxgIdafgjYhTI4XBW7ULow4KL7ai2wl65b79N\nkcirqIxvAtV8afXgroNLLmbrrIfEQSPlFddzPeVNoxjT9bGH1CojksgBbE4b\nibGX98qvh8lgFJQ6ArTusIU1Mjnrk+cDSnFuMSC1hV2ec1mhymkpvJq1nSQi\ngFaLZt52LJPN55MHdm0r1uVJ+qJEUEBjf8Gd+y3Is3kgOJAB/pajB9vaZAVi\njGFm\r\n=+h7z\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"9915c413ced383747e1ca7f2069e170e38517b46","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.b240bcc1b.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.b240bcc1b.0_1576696583302_0.9006078854356365","host":"s3://npm-registry-packages"}},"5.0.0-canary.391674a26.0":{"name":"@material/auto-init","version":"5.0.0-canary.391674a26.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.391674a26.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"d7c9876140fa500d0c6a1d3c6e6f157022481e4d","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.391674a26.0.tgz","fileCount":14,"integrity":"sha512-920Q2s9HaeZvsIPuhU7qwEg6c5pzkMJy9+dZYo1Gp+D/0dRPpa8XOgzJim3P1cnH0/Q5VqfehQHL49dGmLNxCg==","signatures":[{"sig":"MEUCIQCr6b9Ff6FuMpJP55XChw9B3BZRvhjnmWiVtKAJM7NYMAIgBQFyiYSActON0aIfp+2jJiYCUcksH1C2uS8MKPF6hZQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+nsSCRA9TVsSAnZWagAAYT0P/3k1wQwpU6uaM7oin+1t\n2ESHKuSj0p38tCZ/0T1qI+IECw0CtYKwZLZlVSNfTblc0GUuj5LD+yN7vBWH\n0/11NqqVH+zlIZ9X8j6lYzALQ2XD42qgJ4llIOCUgJb8TRu3OKFHJQO/7Se/\niOF0J3D2/Gk4hLyMI3u/Mmg8KeZGuiiBSwEXOVeXgHM/iDp9NoPdkWPPisJT\n+QayxQ9HL/0AiRrFpu4OAf+kRti4oEQMkdXqR+7TmL7/UR1saWakfR5qSias\naV275/esHPeUxcoo6bqzbglsKg3D5Bp6+LrTA02VZYDu2nTAVDtXJd93p80g\nMJc0HFrRb4d8Glg9kuXKZrmHdewI7fVzPqeq8GxHUneF1pu4Ev8+aC5z4L3x\nGXgXVBGiKOXroYjWMJdAIXEnKf/OFDs3crxLSdrRO2PB+9D87ofE4WDVSYRw\n7plJW9vgoH1pHeIUAxTfPRDs/3UIW3ZXsHOgWajeoEI4CTIHmU6ir84jNtAE\nsBN1oh1tKBUiBB6o/Qt7rxmMz30qXWup2iRyIfvKrjDABDqKCmnlWZqnJn7+\nJJL7F7WQZcUu2xl73fbm2U7uycyjiHtzl1A3w+dt5a8vpWIPr2JNI2DbGWWc\nkplBzYLB4FIvgDvp6ODHyvsb2qmJAG3MqKmeWu3Y/0pUDmrkSRR3u4PLcnmx\njiss\r\n=HRCp\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"aa67ddaa5956be1096b1d442788cd4a5565d7598","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.391674a26.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.391674a26.0_1576696594119_0.14920758309734072","host":"s3://npm-registry-packages"}},"5.0.0-canary.c4837746c.0":{"name":"@material/auto-init","version":"5.0.0-canary.c4837746c.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.c4837746c.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"fc6a79283ec0dbe1f56763c07814b922c49ef61d","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.c4837746c.0.tgz","fileCount":14,"integrity":"sha512-i4sg//fxJ3AyF1PJhkpF93xK5++uxdqIwrT7vNMh4qQwSZ3n+LrO3xQVnOjT8/zB1UvvNiV9ReZBKOrTu5gArw==","signatures":[{"sig":"MEUCIQC2SLH3zbC8Lpqx9TfvPXuds/KEa/hZ1zyyd3QFtxt5hAIgYIsEmLBmRcHtRjL1ZFBzjqLiPowB2XQFP3Z/UTQ/jnU=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+n9GCRA9TVsSAnZWagAAkV8P/Rg/IpU2wuVdgS//R+qB\nrs1nQ4juGHssp7f+eZOTb7zadOAZW6kJ9ya/RM+XhU/sKBFuCBU0+9YUaKIH\noc+LqdaiR7YFpCN5r258IvGQQTy0JTKAi1308HL4AtcxjVNoFRVnWhkzzKAU\nJS8NEqxVcb+7PqOBgseHbZBpnplW5NgnaG/zRFncBeanZ5a0O9pua5n/3q/k\nSmpgRgOs6sP9NofI8bXTl380nhvE/rxO+HEuuevgRyPxtFLlGftYfTCiYGdv\nZ9w8SU312KbUP9uP12AS1WH/VQa7WVX0tm+r6gTbKmCY12toh8jTI+fFhSdg\nDNvp9qEurmmWLIzGFhroat7U5v/7vdhDxWshk28uQ5MYUUapnK7d/Xu5T679\nnyIbvAD8MYM5tTEGFPZvLOP0vKUFohouBfdKywi7Jv80cixJO3HcUwGznpJa\n9pJV8yQT2BQnJ/xJInRNRM1pF1NZeS7G0j7eK/vDsP3kPeqH0de4kYoOtVeP\nSDazQtQyVUUCAcMEzCAat5S/U+i9jBA9SC6UKP7gVg7mErAngwkg7M1JoI/6\nISdd2FXO00+F1xrBthg2smIjqCMA457SEH6JVde4pHmXa8ZfGeL7YOZgQM4J\nkUDyMwxVW3kwV0MyjuKBHS7NrrQX+2IN9wc3wGKiLcLybEkLcfmF8+DijZen\n46EN\r\n=3rUk\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"44ccab29aa0b806ec249d5f5117ac9f5d82fc7ba","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.c4837746c.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.c4837746c.0_1576697670292_0.28545530166566757","host":"s3://npm-registry-packages"}},"5.0.0-canary.e41a70425.0":{"name":"@material/auto-init","version":"5.0.0-canary.e41a70425.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.e41a70425.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"04d0706b4904f586b0b906caf8acf6094672736e","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.e41a70425.0.tgz","fileCount":14,"integrity":"sha512-sEMzO8g4VgRxnZH5XyS+ySyVEZFgrpbcZGu+hdV/0XV4Wk7dij0l2uFZeTXuyxeV8quGpD6mnmcTHTZhg61pMA==","signatures":[{"sig":"MEUCIQCJBeeN/s343vPB7iD8Ft6eBWE5lCSKax3YClLMxxxODwIgbdvWbscZn+RLDUpdet6A6hDNx/LcrP1ZBP8rdYa8uG8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+rQSCRA9TVsSAnZWagAABJ4P/18cDF/e0OiHInZ2V6Lh\npFUnwa4V695oU0Zmc14Xo3VbHUj4RJ6cWL035NvUjffNHNIhk9faujOAIHpG\n88OJa7qIWm2s3WPWpKiLfq0rOgJsgawhooTuuINc4CgFFVKsW/C6urudIras\nxaDHQ2Adhp9P8PkTwadyJ4O3Hcr2Bth9LMeBiR3Of7jYbhcHbBB2iFfwtl84\nraGKWS2oU2zsTdEteClKVPZztNgooUWO99sek1ebE0/ncr9M/dIsoKope3SE\nWJzqjNeweM8IRYUPCJPQGFjX5PE2XAgKhXOn2TUs0cBsKAzgXQAY57jsFqHa\ncFIHhM3sljdOzgyeKFEaIrsl42m0wtfUzqh7ce2nSaYs8GpoS9f6kPHLbGBM\nC0gBMOgmq2wDhxumpHNunUrmHoKlo5FS7KXVChtVASSTb9WyijA2rpRTMHxI\n26NjQcUhNbtmllQ7Cp3MUUc1tejqP4jB/HZsROP9mLEV7TlEAimkhH6l1AVr\nJZOpl7WuyORu/NqUYLOYpom9Vot9T/3PiVqikIcbNO4hdrA/MmkO6KKJRdsP\n4Id603tp7DQPVYoF846Az8zFWQn1UDZKCpbZ6YuqCFaTIQ8MovJ9ePffLvkq\nanLeREm/e5Vt+iqEY1W+ofs2YsS41ZfKjoq0010Fm9e5XyIRAcDj9cMrbnLz\nV1qj\r\n=NTaI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"2e938a63bb3297bc73cdf8f1f206885e2ec84a6c","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.e41a70425.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.e41a70425.0_1576711186208_0.02675783078753291","host":"s3://npm-registry-packages"}},"5.0.0-canary.bac43eb43.0":{"name":"@material/auto-init","version":"5.0.0-canary.bac43eb43.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.bac43eb43.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"c01742de892c1231f229f550b1391c8ae4102660","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.bac43eb43.0.tgz","fileCount":14,"integrity":"sha512-B+WLCMn/GyrWmipiOvLt1x1z/BGjf7WumLr6W6a/hxTZAvDZL93fngm/0Xe7oLuRP2c7Z9hjTgdiqN7ezdmNxw==","signatures":[{"sig":"MEUCIEY2jBSkXzamrQfzvFVGIAw4Z4iHArl7rlS7Y2oQ1T/1AiEA+l8ig46RjQDOq3DD151JVRCTrV5Pl4L8wOh8LLIoFVQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+rT5CRA9TVsSAnZWagAAELwP/3VCqR+za927+SN6iPt4\ne4pOn/uaPmmUpcqJJ5hou9h+I/KB/tfvS0z8oyh+RlN8iJpKGnuC3VzhGpWG\nBZ3zAN13OX4Zmqa9wKJUmhs8AZ8ehKGRtZgZeHNDmhhmfoJfZvquwwmjGFXf\nxdlTc23eMIfLR9B2IQZMewMRSE5WtWGntw1ID4mpUKb32TX4YixI8mp9RLaD\nAvhXOkVPF1GZ6ke4RseptW6znSeyFYJ4COzEmK1TUo5fl5+vy17zzevjPPha\nshpuRllmstYYZ4aitZH7ipmJ8WHwthhMmq2f6hkgx9fqvE8ML+5329gl1eZS\nralBmUrT8CMNVGySBFyXf/XrM6JxoUn82qQzxBGGqwHRWI2WmYAwAkJws0Xl\nVWBm907tjF0qvHSCZrADKSZxEQPdgyrwDRqcWM26i2Htk4+KJV344HfEpno0\nMs31FjSK7pSoMVFeiGgh+DkPmpdbHXzPqTSG9hVg420NSs5wwoRGPOuFcLZg\ndPXZRBIDy0dxr2rzwefG55tcMwYLWvWWrAxVXUyMUHJ9ArXgUNvTLQGQVoKu\nZf/sH5QnY2oMFL5lu8UvIZC8Jp7vnsTXlOM/mYHdlqNPoB0I4gLhz8+wY37L\nYNxObfh7rWO8p4Rqlc03PHMtOLea+jiwRznCW/S+9fiqJKQG6mVTwk2Qa66i\npo4I\r\n=Drjq\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"7035dfa39edc06f1b58f72c5e285bd2998747232","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.bac43eb43.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.bac43eb43.0_1576711416665_0.11664706192692154","host":"s3://npm-registry-packages"}},"5.0.0-canary.2e491de55.0":{"name":"@material/auto-init","version":"5.0.0-canary.2e491de55.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.2e491de55.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"bf14fe798df3d69c39a9d5cb4ff1adcf75cedcd1","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.2e491de55.0.tgz","fileCount":14,"integrity":"sha512-kWE1bji+jEh0C4Kf+vND+A3Jhnp81vC+wzImXFaIEyVRFErMGk+5QyKqCBwQb3cS3pTTWv4FFeswdl5/c7tJdQ==","signatures":[{"sig":"MEUCIAHIGv/t8k28r/nhkVxnNNrhXf8p2mMaX8z8EItxdjBQAiEAr5F37u+RBq7Chd2joUlb5kqyqGSr2F6uFHnTv0m9w2U=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+1WyCRA9TVsSAnZWagAAhK0P/RRy/UkLua68AvtteBr5\nWh2kC3XGq4E4pOAVWSwmpKsQbjMNxCN0fr2uHiahhB5cNJSuIfA+LMyz6e9W\nxn2UZH/OWJykP2x+o+ig1KAHY0Dgw5pw9frUQRxVBljApUqQ3+7XCo0OmBup\nNTJaqd8p3XH+qnTq7CU+0l0gveEifrWcZFLw+yGskCh0qqP4pjp55HEwpbyR\n8Gpx4hMCdEbDIARBcpKulSOi7s6/MpNmJdj8rkPJLzCrrnO8/uCv1zdwaGlN\nIigpxCs9qWsIeQ8ojPPSJ7yY7KxakK4ZiSVLcw9E9ZBtILjCybAx1Iva+6IR\njMl+n+7gYRt7SSO6pCgu0HNXaIEhtjLGRGJv0gl1sFnUgKT4crgHtsE964kk\ndtVqeopbhCmzCqm21YWNmKuDeJIaDtPzNFkf8IT0+oy5RyoxxsblE5Y8SEnM\nU3LpPASOdjBHm+SO8arkJigaSZGZQCBtpQvhUPmGdQgNrHfb/Hvub5ckWFOy\nCnIAvTo2xLa8jDFrK/7Mw7OmXOyy6JX0AEQg969mnsKXlRDugLnqr9gQupiA\nJxw7NveM4voIdhcJoIJt8y63fpUA6t82gKF88NqzGxrA0w+tNXD9oUsNf72d\nt5SzRZSMTWlPhjzs+ARVii2Yzhdaj+O4PJMROM44zhSt3E9NxlcxR+/tr5xj\n44ol\r\n=/o6f\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"731b98f2f9caf1251d3a82a3abe09828a92eb434","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.2e491de55.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.2e491de55.0_1576752562024_0.5595867346098535","host":"s3://npm-registry-packages"}},"5.0.0-canary.ae101c144.0":{"name":"@material/auto-init","version":"5.0.0-canary.ae101c144.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.ae101c144.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"95078727e4cff271bde6920544a90132622967a6","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.ae101c144.0.tgz","fileCount":14,"integrity":"sha512-IYABLlZawRdFls+B1ke1ycR5xpclxQqJupyEnSBJ5x1uxStXQ027tdmM6R1LT6WUeFj6rvW7EcN1dHLValwWkg==","signatures":[{"sig":"MEYCIQCDSUUe/ZcLMW7F/MCHApoceVO9jHorgsQCxvFTseQiFQIhAM3ENXAESG9MxDwf0G1GGlxgXeMWfj2eKkT0EYULKPRl","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+6Q4CRA9TVsSAnZWagAACVMP/iF9fzvNsYrH6TK1W6Jr\nCLbhUpYn0uNW0VXxoMahM0cabg74wRjLkdYo5WovVbegh46ED5ySqKcFuFY8\n+OXf63GWEgpmYyjh8FxrGDgB6A6X3HBBjiHFzrEEsY7QUTJwVNGtGtVu5aFn\n20p+pckgHw15uxtD1JHnPd1+79kU6Y2IVC9+2aaC0gQs1HNWiRopOUCdk6uu\nYi2meEacQpWte2P97AfbnbNoenVp9qWk3LhywXGyhSMoFe97pyPkLZWEP80B\nn78KN0BGscNzUcgpfca44UNsm3z9D/tWeXwi44sEVqXlXtfN5RZZJDg3hzPx\nLpB6znl91qnsdKR0dunUeW3UX/OhzPM0mnzw//617AlBKWN0hUlRtc9JCDPX\nJ8RKEBmjGHhC3K9UgkCSeONhLAMN+6BNq862sPgx7aNyUEFweoJOWEJj6S5n\n+Ss0Ht0VX5SawyZz5qVeVvmw+lhrnH1mmfZcpYCnXguiHUYQORKNnUaflZQj\nUMVTen+vQEyFV30U8O6pVYws6hc7D0SsrLu3T4J2JWChbSMROu39/8qNBjXt\ns7B0g4bzhkj8eR68/0xj7rI1fpUkNpBQyRiFhoMVUf/pKdP/pvTBy5qYxnRl\nHe0lFA/5bN0xpQVMU7xniE3f3R1UM1lpUsimnIRzgMD8jtK9uLcM8/fTv0O2\ne8Pj\r\n=a197\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"d11f348d85fc15df510c3e33822ce23f44ee661c","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.ae101c144.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.ae101c144.0_1576772663519_0.23400312511939325","host":"s3://npm-registry-packages"}},"5.0.0-canary.a51c31f26.0":{"name":"@material/auto-init","version":"5.0.0-canary.a51c31f26.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.a51c31f26.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"81c4fbb1ac37bdaf1d310d73b2743f090bd0acb1","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.a51c31f26.0.tgz","fileCount":14,"integrity":"sha512-rYCIIp+klZT0sFZg10a+Tqit40oK9hyadxStoxTlhTUYQCR+CmAmmHrVv4hSEGUP0oQnKtvnfuovVzLpj4suMg==","signatures":[{"sig":"MEUCIAJSgxBjN62XRyfKS5Tqd4KQhC2JtiH1a9rwx9Zbms0VAiEAxaEM+A8bmz49MjqR+poUomjf2Nfs7F+ybqDgsWSJdwk=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+6/VCRA9TVsSAnZWagAA1EkP/jz49yxEXOxD9pflsmF2\nLXw6z/4B+xxR/3Wy3qPGDOpQizUQhVqNohjw0syaRXt96K/WFobYoE9UEAFu\ndZtL3EkTlaJMYuNEYV/eMmLtHzIgjZnDEwe8GpSXY+a87SJ5trAFlD5ida3m\nkjs95rJQeqdIX5lHdD6/4s+424cEIUyQrY1OwqHl5oJH41iL2auMkvGpYBpM\nJIaouelo3NvTdLmIJD9qnhAQh9hpxNNVXb5yHY1OMAEmyMeV0pjkZrdUdbXd\n/muT5fTWy3EXDtc+K9OoL+qRIX40JyYbg1ToR8w56sWVeULhkZcaA3Hth1+V\nGSJ4K9ilMdyNQ/Qbh/dHPeOa02najPHghz31geIwiBjovVLNHhmSrHGUz5MZ\nv/ZQYpuBtahuJObIQNC9gylgp3LQIdmVi5CO15ONIyMNZio/62DSS6O8gpDh\nCBCZhEp9w6wyAaB28RM5S1lXGw6te4GiH5s4EyqFK0W5qq4wmU1LHrb8wGTF\nDqH8wxW0ZCiTNg2QKELdP1jTRDxfzLYZ4Uii7WyDqsz3CCUYtFEdkCP3MmQj\n098BYpeLKc3vnT8IfhS8xRZP4/Zc7LmmmyHjgejwwxBxuu6VXmJPXzWXGWIj\nOwfVgpSNHDzApfsLIhyVwoqnnRon3lYI/IiN8Je+BKjmNNmnkFhG2UkW/BSg\nuNUC\r\n=PJZh\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"e2dd52b70a7e3cd011647222c15955dd4535cd6d","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.a51c31f26.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.a51c31f26.0_1576775637539_0.9479321676596959","host":"s3://npm-registry-packages"}},"5.0.0-canary.21fc4e13b.0":{"name":"@material/auto-init","version":"5.0.0-canary.21fc4e13b.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.21fc4e13b.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"3c572f39a7a9affe3770f815f4134070a986d942","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.21fc4e13b.0.tgz","fileCount":14,"integrity":"sha512-ddqiNgBkmBHltCvWkRGPlpybv0NEEczr/eu90oOCFaeSxHerXLwvE7Zqsxe48al0QVlce8ld2YTyV75tnIY6Zg==","signatures":[{"sig":"MEUCIHB431h+XmmVgYMlQhTfRwIg1HgVmWsmYthBmEt9cCxVAiEAmTRmncsaGaZWT1cv1BKNVvBWbyAlnWoiObnTD8aowhI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd++sYCRA9TVsSAnZWagAAeskP/2j1Kn/3yHQ9lHOY2lG2\nqKZqchpbF+B/L8+mkmftRvNVtX0QEv5LpWBShcYeha1C2ulqbUNk85LVibbq\n453mOvofrG+d9kzdryxQ9535VZf4EAaYT1NHgbMpLk4AiA9XGRO7wlmkdeoN\n9/aKpzvrPNWcgJuxyZgigLVcDR0ZbEM8afvE+sNqo96CMnWJiu7A4ViLM5jK\n7JN3Mym7n2Od69J3FqwOYq3uOT1PH2vBof6yD08KKiUXbmV+svxszS0azPln\n6/EvycYrrmab8YI3yBBuSLbq4tthXq5/aw9o68KG8dRqP4NN6/5QsT09D03g\nPevyNV9HOYdr9jXDCT6ls/dqjEBm9vIghI/Tn4ALSQdTSyTDmlDTIZDv2lFT\nfFxI2WbCbT5lP1KZUOVhwOZwfnVjVjRUJH0uQTIOGWwMYg3hjy6CFw6/Q546\nVODTNd32X3zv9gzfiFqLjYZ7SrUBM1Vt8bxf7mvcFQi6Pkt0tiU/fOuOnnAb\ndTEmQuQwiovFQw8GGARJHP+W2dQVh1x9u4xug/A/InFS42CPEXYr3PPQo+92\nRgtai5CU6SRuK+HAjGjfKaqUDZvFjTtKLZCLb77qDva5jxwjS4tAP4gcZit/\nMgB+yVpzLvkMKRZCP9vL19kAZFFvKsROS8GqqyTvEBfKUeI8A+8TNjEwbwRn\nlSYY\r\n=my/x\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"ca71d599c2aed234cb9376ced1aadb512b071fb8","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.21fc4e13b.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.21fc4e13b.0_1576790807734_0.4360108391949029","host":"s3://npm-registry-packages"}},"5.0.0-canary.d2ae6e17d.0":{"name":"@material/auto-init","version":"5.0.0-canary.d2ae6e17d.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.d2ae6e17d.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"43d9db8d917d3377885dbdbe130456b3c46c6f89","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.d2ae6e17d.0.tgz","fileCount":14,"integrity":"sha512-wvWHltvLkwoYB0unKrKpwKggt8d14AT+g+cxjHpG1xAWe4K8S+As+ZN8/jXaR7GJ/IravQlEmaqkQrfCPGqgfQ==","signatures":[{"sig":"MEQCIC+O3JAn2QPWxutTOSLehES3Kln3gka64qE6B15BnPY/AiAxwH0/TpXSLyiWDW+hcPAUgZHb3GPvPHgc4cZvTji68A==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd+/h4CRA9TVsSAnZWagAACF8QAJLsQKWWUbI4Y9ZqnxJp\nuQSL1I/BC8IKcYhNAEZ/YtpZDnhwOcvN1RgQiEeMATfUWs9aJ7kUGeADoZUR\nmEwuwDoT+OM+Gc5xJfOxoaUoklHMHZQn5LbaHZ0C0d3KXH/jBnViY3si3wul\n6ha/EiqYfhBmz0onX/5cOLxitxjaq8DuZ9y1n5rDNniZXSo7VHC5FsFriA9Y\n5xgmI9pxCqjOQAxeOXbutXTY4G/ZlKBwf8rbXwE7rmhGQbHRCZeoUQo3UcuE\nOjla/iqO2ErG8tWU+ZgNROdyAv2RrIb1e/vNPbRmprXa8YSywvFolBCYjjEO\n9Mkog4W+JtZzyZdeALftSWIamUv56MpDAoR0qdy8ONJwPJ+NAFu5ZCJYHybp\n/aYaNqG7nJiH5meUkHAE3DSEoSNvIlIEXYv7DuzVeNS/n51PV4MVFm9bu/RL\nqINwxG62BgsMGLtzELQlrG3ue57kkr++zPMSklfXtQJtROmh2rYIt0qQTHw4\nIgptySvtyTN2Q+zpGriWVY3r3U+bXbKzLsm0kM6cHp9wftolbXhYUFqVL9Gb\ne4ROBgJB9KLV+KuQcq44sX0xhHlP/bQtzJNzsnTZiemh+bTiuk2O5vZUOqzu\n5bYUnvSJycJRw+Fs5CNHKDQCxuB4wfRqRF1Zxp4eHXzL1WACkx5SNYOfwNb+\nP9Km\r\n=h2FQ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"aeb622d14d533f70c26396fb7db6c8bc48eaf8e5","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.d2ae6e17d.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.d2ae6e17d.0_1576794231707_0.7112183166192034","host":"s3://npm-registry-packages"}},"5.0.0-canary.ba30399ad.0":{"name":"@material/auto-init","version":"5.0.0-canary.ba30399ad.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.ba30399ad.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"08a7c3fbe9e0bab9bb273f38a8bee4cbc728e4b1","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.ba30399ad.0.tgz","fileCount":14,"integrity":"sha512-MzGx6qJOERhS/cO9N8l6NRE5Iy2x+YVn5JyJoB/JhMPt6LRIF2GTVgA6Tyd//PtWBHRUfqn5/IhxL5UDA1CrIA==","signatures":[{"sig":"MEQCIDwntDteVTLkp4lEtBvwAQa5F/JIpqxIX0ZW3iduaBwDAiBDHGU/QGQr/1FuZXCrchE6JioekT8RvYks/nDn5n3OUQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd/B9BCRA9TVsSAnZWagAATAcP/1e5XSlNwTEd009NjuHK\nzirl2S98efdUeXqQVuZD97qhtcmU6fULIlr+7eM5afRREqJQT0CC8vz7KF6h\nUSHd864sBbOudUwYDrm+qlawzq365uFtzqggff8bH+hSYHiNHusWcq3qIm4V\nkbf9T3W6tKrfSgzI099mrG8WXQTC41gPCQU1T8VoiLf4u47fkNn18QvK3S1u\nORU1CFrXsAPUfNsQDTZh28TlXjtkAelnOgQH7OHTkJcs2Ktd9WaC4gBdpIkX\nv+pjEM08j0uv9JUh6AMXDOd9LzqxlH1qfapCvdnt0+O1kGB09zVmGX296aGN\nJDmV/AOUYzJ2JmknEzECxmuL5GaQi7USDTA3rKcfAgp+7Wd/bSDGpPsRdQVx\noK/8Sq0OTjoL0nzzX+D6aE6gX5zmCDVLj+VooAoTwCCGgr+n9tRFbMgwfKLy\nZaAPv16qbajQLw3g5zuq2f5Bon2fFop6FeIDpPrKoSCvcCgGec4sXIzy4gei\nH7Byd1pJDiiQ17W155tfZke6ABFq4dG4Pi64h5ELYGFrM/aoXcMOroPesJnI\nMTdo9FSM6KPGXtMdRiFylqHqF6gy9d4+OB6Y5PhHiSjDZHx3bwkoHTtwV8Ve\nTOl4Mt8HWPar/YNCd4h0ME3v+GmzFNnpLbkNUkxUuaoaj/2dND5wwIQbDRa8\n2X1/\r\n=53GE\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"75ab7f122d8d469963211d9f9591a84602711f72","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.ba30399ad.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.ba30399ad.0_1576804161124_0.9271028814563522","host":"s3://npm-registry-packages"}},"5.0.0-canary.a08ccec35.0":{"name":"@material/auto-init","version":"5.0.0-canary.a08ccec35.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.a08ccec35.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"b15015be9e4a368d1aaea3ccbcfee7e15ac34cb1","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.a08ccec35.0.tgz","fileCount":14,"integrity":"sha512-XKanogpUCCQ1Hc3RbKJZCuwjA8U09hmC6jOulTfSaKiLRrDB7eSa0BKo6Npbzx9Fi2pwRWco+dIVF5IB3+Kxfw==","signatures":[{"sig":"MEYCIQD8FW2M9vJUaswcdf1HNnjEf+QqA9Yjb5c7AwzC1zCteQIhANrP0LQFl5or0W6h8N1/B/dKp7Lse3urBHJjkA2xMn0j","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd/ViiCRA9TVsSAnZWagAALr0P/11tqA7WDLxE9mpzoJM1\ndQloRy7+/cchmQpDmWJolKxV4mLYdRWgghjbNHSt2zDFgtUfGAlAiSNDJ5RE\nuSLr0WSwCTFIfbGtIz2uqzrBUYxgMy0drIdsY2lK88BoSnDH5IqSZTGRpGnE\nDURroHCyxIUrYGQSbsIIzB0sjScxUSkEMaizGLPKEyhIN1RxnCmiZjQ/u2ig\nXgZRNqU+nkDywrokjAwZk3HhpJ0QNZg2hCiAG5r1F4ZIogNsHnIm9KMjT7Yq\n7FbOQqnTOafr83u3P4Fc70o5xl+HyMplU6tL8RQy1ku4FDFHykaK5125mJuh\nAosHT0d3cQ+dVAT6x5vZVnEoTQvhHsNb4k0cDTWaB4XxRFj3Ch1pBVx1ZJKl\nGWS23kOGbL18Ty98eB4kJNtVsi0eX/Ax2KyeYsHiyOolykK0CyPDwzN6tTJ7\n4ew5WQOjlji4a+eDskmW+HnZ36AxGXD7GaKWBhRL8GX950/oqSVOy9gMHn6M\noBHd4cvwRox3091Y328NVk38CyXomBmedPxxFlmmTmcTvf1G/6l3ASk5AytB\nCmh8uXIxxwgTVp5kMTo/vtfJh46w5LG9tjTp3kqi8XZvx2ojS5M3EMWTnLa5\n1NfE26uSQJXS6L3/v5YDhFLh66c+ENxDb4pDkNPb6eCSO6jA3CzUGEHXtMdI\n8NCh\r\n=rwsx\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"121f2cfbbcf425b2c92760a0fcf0301dafb14636","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.a08ccec35.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.a08ccec35.0_1576884385885_0.2227336624107732","host":"s3://npm-registry-packages"}},"5.0.0-canary.a2f75105e.0":{"name":"@material/auto-init","version":"5.0.0-canary.a2f75105e.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.a2f75105e.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"a8f308d52c19ba6431d74c1196e770fa78e9065d","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.a2f75105e.0.tgz","fileCount":14,"integrity":"sha512-7qkH66ydCRm3Fl2CwSdzENjYEOtFUGSU8vJOiIZwOsvBrNnvI7oyoITwPgeijTjwV0Qt4YXFHtv7Hg9jgzEsKQ==","signatures":[{"sig":"MEYCIQDAy1Alq5AzTY3X10l828v+5Xp45sNEu+mRSGpM0MPtqAIhALdWUuJ2G9ClCb4xflkHzCrwIwgSnfWi1Srye7pEnIQv","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeARnECRA9TVsSAnZWagAAzCkP/iFqMU9krVaCTfGp830G\nrmcCl+Tu3jQ/pX9sntRdLtA/uawwWgPjS4KEE/o8dBLd7J6HlhjnDgjFZBS1\ns3hPrvS8EmN+dsjWygjx+Y0ZclxOkBZFZN4MrfFipD4tR+PCMGltgK8sVIvV\nBJGtG9q2jtT+PSSUrovCPl9rgE3S3NmMQY+7vqzZnVnID1SkBXhHwAS166kt\n8ltO19tDq6uofx6Tda82j8fHSU4qCE71whXR1F0JeFI94LRxEG3R0+K1sfzq\njK2JL1nPC185JhOdkcbY6175aQdaIQ8S0at8Yh08tsmFyXSH7Jo0c/UvAr/B\ngNJqgNhLbMmmC1/pQXIcZty43U7k7epO0vr+Bhs0r3p7nzSIw9/8p75dX6k1\nlHCW7Go+kmQ0m1QhyaNcpqo2zeObdLSR4EwW6dkzNCG9jGvjUazKLCuaCYd+\nxkcxVCPN/pKQnr3oy/rbNZqHHPneIea32IU9am+VcHPs9cxXzV/7hiJxhy5D\naoCu5T9vyUVHe1TPBR/WuBioR5Hc7Vo4AQnw1D1v1K6grHQid2/yMhMVmArq\nkuORIoyslcJ2+FxZ1ChJAYgXFBPNoo0X1OwxNvGd6YVHMGXkJSl9mXdOf5NO\nMEcb0qmBG9WutalE5lcpK0og5HXoJ976vFZnEScnqyA61D9UcSyK9i0RJGEA\nYi/X\r\n=B34+\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"7b2f4b595ae59e3e680ef1151ab400a3855144d5","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.a2f75105e.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.a2f75105e.0_1577130435953_0.974669766906433","host":"s3://npm-registry-packages"}},"5.0.0-canary.c054a24c7.0":{"name":"@material/auto-init","version":"5.0.0-canary.c054a24c7.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.c054a24c7.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"e1208f66526033e0409d887b08f61fc9d29f8cc5","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.c054a24c7.0.tgz","fileCount":14,"integrity":"sha512-v5vOF2/lxlEwdckBnMFuv2Xpqi3C3cdG7c9g0g15Y7JFI3Co6vza09yely/tZlm5GVocm5qINHHhiFqEbh7rvA==","signatures":[{"sig":"MEUCIDVxqyOFiPZnc0eSrqXq8vxzkjs50X4yXy1oC5H6tuw8AiEAibVDAig9whduhOkHIuV7dg+mKzxDO10mpfJpA1Y23SI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeATZyCRA9TVsSAnZWagAA+boP/iDUvdY3fpZgVLTER5Sk\nZqMl/r+GkzpZaS9fC5CvEVjMdmdhVF7Fa+4FHJHC+BIgG0DY0PshE9Q0bL5i\nGs7KRiihCgrgX957gFIK08S6r0VduUCW+S0m6Fq4VvvzU1j8eMSBwJFHQzOT\nDSEDsLWIrwVZcumiQ1CoCKJK3nUgmauDvC/yddIyFwfcnN8NgkkkpnjYBkoJ\nimXLRuqBx5tLD1WkFu5CT2DYfbkrcB6z8KHxHZ1z8IJF+r78nuXTHKp1VfW+\nMaFi2w7kPwOBt5w0ncGt1n+OujK07tHcaZ4wVA5MpiyIFNxp04KsPn3eHQ3a\nJTE2ohe3n9GlPv5ORxoXL7pcXGP/PJE0+SneIts+BiJuPC3KMrsbAZ2g8Ow9\nownG1EB5ZcIsU0ipFFKp0QSImmqaW9Ce75n1dIDxMcRGJ0OCuFF3LoUfAaOv\nDkCdKrHktmVdUDsZUMaHOMB3coyv8/UApJ4LvdzAVXOsJqBa9IfMxan7W6cP\nQQ1VH0pXe7Vtx7HvyA61Nwcwiqnlily79xxP5Z8p5u/6j/cKYZBBvUxh2aia\nJ5HPs9d+E5OjAizZmXQRp6KWZYkENb1e+334PtA6mFBiTYNYrU/s9ZwB1Iwo\n+8nKVg/7dGs9lQGVGj2nXinDg6MrkdkTXlLdZFX0osRvMmXeZbRUG0TrcpwZ\ntvOA\r\n=i/Bo\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"4e2a3c12859a131938df8918a9f43b9146056488","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.c054a24c7.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.c054a24c7.0_1577137777553_0.21259185459322238","host":"s3://npm-registry-packages"}},"5.0.0-canary.c6808c51c.0":{"name":"@material/auto-init","version":"5.0.0-canary.c6808c51c.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.c6808c51c.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"7f2c2872c6e9f2161aaa9ade43034cb8ae9ebe04","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.c6808c51c.0.tgz","fileCount":14,"integrity":"sha512-i/Qtf5EWYibWYKNs/IKFC8fjwBVPRhP8Qf0ils0Xb2alaFrVXbCgh06EFzi/185IKN4ce6Kb9BK7zJ/WHBJuvQ==","signatures":[{"sig":"MEUCIEnK6wKsIm/5/ZC2Ke9SgFuWYkHUmRsOfYFSC2N3J7fNAiEAk2oiP8ZP2zG6nceXI60JbSuPojjP7LN4ah27VmwBYN0=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeATeLCRA9TVsSAnZWagAAj1wP+wcNjOmXGigb0nzVu4Vl\nQp4smMo/FGZpxYAeLXI991Y+wMJWQRiI7y73tLLHFJv/AQMe68wovL/xPOgB\nvW4hgymQSvWs+B8+rI1yH4jHWzCx9CdlLHKYm9HM15Ow82eWBKXhBNfBQ7nG\nss7c+cvGHRLfCf3QsebtTA+1naLB1z5Jxgf9xTYgTnRy4wQp37opFtljqFIr\nVjnbECoryrEpEYfn7azZ6XDGYF5STxapivZWUbPJ+rhMux3aLRVEkd+rcWkh\nNbm9jJ9i2Ba05McX3UWJql101c0yw2JAoFzzEszYgfAekSLIqrJ89haciMcb\nWzzzwG/kl6BbVGIP8giJyt60ZI9G3SPsXCwHgJnbjH8xP8+D+CmDu6uuFaR5\nZkWZZo5dO8Wx7akyLQ7rMBjrVIsCJeiHp8hvBbFuAnyr95OC/cq7U7/dd/Lt\nvgEZR5JWVrUXmD5NaYXHr5LW0vPkEie0s90p2rHCy2w2WBmSeWuMKOrzhAa+\nnbF6r4Oa5JcB5VBHxaDOuws6V3/oAPUUFd0ntGegqQaj3FDCkrP8rY6PH6Zm\nPBS0i62QHBpS9g91QbaEF7tdmTC5OlKx0rJVHLZm12QHF3E6mBXv4Hpz3DGJ\n9ePcEI+OzdTEPZaaxXaRl+S9hjn42PPgCfLHRb8shRVJLdYvRKaS8FzrvDf/\n4yxX\r\n=zP+k\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"02ee460be616b30da3c6d5daa7eddbc5f29d2500","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.c6808c51c.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.c6808c51c.0_1577138059529_0.7412094180950424","host":"s3://npm-registry-packages"}},"5.0.0-canary.7bce9cf77.0":{"name":"@material/auto-init","version":"5.0.0-canary.7bce9cf77.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.7bce9cf77.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"c740d71e8f5b9a0c85805f4d91b1e6e8679c4939","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.7bce9cf77.0.tgz","fileCount":14,"integrity":"sha512-C76lZRGFdZoD1imgyCYtzN66nHZbAdn2AwQlWGfxzie7NUx+WlkOrmVq1/TPYWpwzk+r+G8w/5SCnejszbYcpA==","signatures":[{"sig":"MEQCIDzagWWe1weEO7JhTc4wQdNmPsxQ8HbGDwPv6vQl+hsYAiBIpuPGGXXDebPmhjgRfvApNDJptIgOmZ35AzfJ17W4Jw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeBP+5CRA9TVsSAnZWagAAtG0P/2+WiJps64TW6uyIFSqP\n6f1X2Xv5rl74LfC0C0fr0R2DwLIQhZE+UYew/mSyZm6Ue/VtnEd7Mu2u0iqX\n+t+aTtZvHXg/ImiZkhr2kMOL8Wa2QwRdaHjPCYUMT4/RzaWO6lZ8Xr6JST15\nzk4q0VrY/NeK4KI1HO4LBpYnByoyiJF69WslFujePi4HJUY4o8aWPi7TjPEP\nxM9OeMVZyBWXWtN+zdx9WVgCHuDViuU0zNI5pkEqfw4F/W18/TtNaf1ADstz\nlKHilRpudM55XAqhJq+s6GPR5svleoapjGL6QSQM2eQO4PSiBVQOdvhCOQ8i\n/ubFMpwzgR2BLWSwgyU9Hbtof6lCP/ZbegKUgbgkkchEAY0Ks9RBAkJNS4F7\nwFvyiT51jEuPCKPiSMNjJXSsg394Eq6+4bqK1/dSQ4S/bcU+m7jr309PqoMU\n5pIhzePxjPuWIX6b1Sc551r/as7X3vyJ6I76bQvAfgEXLu3d9mpfpuuzWF5r\nEIpQoV2Pi1WqifKwOsHVsNWCjLh7XhxRnvlAh1d6Fzy7hfDgoVSDiHswK3e8\nTSlUSkVlYFU3Xko0en18fHz4AmpynHgK2zk+maBflp53TYWUs6V4utpgKWwA\nJlNcWGbg04cGPjbWe3TvbBUIgMgWFwe3lSYd4Ip4Gn31VFk2ce6Tt3Qu5CgQ\ni0uM\r\n=VYp5\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"1f5c1996d2328a53d1fc5cffe847b04aad48432d","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.7bce9cf77.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.7bce9cf77.0_1577385912549_0.25494685337155","host":"s3://npm-registry-packages"}},"5.0.0-canary.c92f038c3.0":{"name":"@material/auto-init","version":"5.0.0-canary.c92f038c3.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.c92f038c3.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"b5005d833fa3dc914da337696ed4d446ff2b97e8","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.c92f038c3.0.tgz","fileCount":14,"integrity":"sha512-eC6sN2d7uQ3XpI+toQD8js532IHUP0svsM6YvSWV84j862HN+zvESrn7GT2QHw6WzSEOkp1JoEWw4jZ2Ev8aTw==","signatures":[{"sig":"MEUCIQDM6iVPaJfPG2rWdbVABJB1ghSAjerI6JFblWLkM8XqjAIgex2bPylRjWQGTC4QWxuoIsuLuxGZDezVLR/Y712SicU=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeCnQLCRA9TVsSAnZWagAAIyMQAJTdonzeP3l1r71ffbhN\nD6+ox81KG2xfMlCGZQ9NWnlnYDkUKys5ReXvZmadjem1jrRkPyB7JiYlzNgN\nzscbUM0cH3jxvGDMS+/s28xvfb4ON6zm2iDNMXUjA+x88D0E7z5f26ApQ2b9\n1NXFLW4lr6fvKC7INgSZJujlAxZchxYm6WhjrFeNCK6P2dAqEYYV6clOrVxC\n8U+zuTjzGk/ZHh9LTxMae/YhQrUJbPB9gOBCsiP7yyDpf/kZIuRDZlzpHjCE\ntSr/LVjYkTOys89xKC0N2XMci5SZMjfl8DmnhpD4DlV+lGTg1rJeBOA7+QkT\nvpNA0WTdqWuWVrtDiWWtyL4RWZB7a0hdVkx/xchLTyURZykmAFCSGJvhBfLh\n1/xXtTYYEVqc8Ha1nqnY3/mMZ/UCSjePCKsb5ig72v/Jp99PKv+Hx1ofI+2i\n24kKW34PVpuqXd0pF6fzjbQb6BmkW336AH9I4k7UUqBevAcsGPw4suDnpluX\ncJvOdfMHfQlDEX4ZnPPdDHnpmKZmIyn/64x8HGMNCD4AP0ZSV7PMEfhWU9Af\nj7U26pxtiACIr8vawAjOHnKWRFc6rnxkNRKtNUh8qT1/zvascps8C6Ts/qi2\n8ni013dGCSSDHtTEehDBSEFIu6lSnnmmaOlS9L3IPhmQjQn9lUguE7r1eQWg\nEzka\r\n=jbNf\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"823f4f89b39f86d10ed69fa8a943c050c2d83a6f","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.c92f038c3.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.c92f038c3.0_1577743371089_0.37560033462510023","host":"s3://npm-registry-packages"}},"5.0.0-canary.1f1ac7558.0":{"name":"@material/auto-init","version":"5.0.0-canary.1f1ac7558.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.1f1ac7558.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"739e7d1b311c9f3588a3cacb348c80e7b6a19809","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.1f1ac7558.0.tgz","fileCount":14,"integrity":"sha512-D0EWFdjLW+qhrIVcYt1kon1AZOy5shlarTUA5OnbRIfiPtO1i8FS+G3vNTB3DtOAG55BsgeBEIr5DjBPfO/Bog==","signatures":[{"sig":"MEUCIBd1iDd4BjHR+tk3nSG0Pe7aO3tHwlFNW+l5jzySQLn2AiEAzZlPyyFdHPKjBb7CyNL5X283VZxcT1vMcSo5NWOmFNQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeDlhiCRA9TVsSAnZWagAAQ24P+wUeTHTZCjt8ao7WfiLc\n2zri4HyqbwKajEcaPS3i/ua5iyKUs/CWssJ4JYmJCJAZMJp8lH28Tu9MRxmW\nme02Jfgbj+0uuV9oqY+2qJqlfC8gwhHjBrlZ5/mumEdKTrcqj/VdFl1Eufg3\n26Vo/nRK+n2dnUYId56YY5FgaBG5RlLLOsTvD/5RB4tz+v1aOmgdaS9l6omy\nOrS1pp1TEp8QGbIYzvglqEC+RIWiLJs3wRpEh70yJ8ez8Ui8zmqg3Bu3/JQI\nd3D8ZYN+9SNNXF6ImU+npnyJ860OCh3DAmd0Q9EeRJKmI0lPZkpE9vCGMXMp\nUndcqy/avK48LtpyKZPjWl1n9e4fyQZCdfbprKlfgBsWpBsbXE8hHKOkdttQ\nGN1a4eCh+oqyhAmK8XPfJ9/zdkrJjqt95EkbNG5Wiu++TIOmTbVv3whSzvxP\nRnWpiSzqYweqV1V8Cyn63t6S0DInWW0+dkpRcdO9XsKNdKNBw6M2ptuFEkCt\nRq7hAuGBczUtBc6KE/vVmXbgXFvTF1ZPRxVTZzlXTySSdKjAoa8QCKo1w5pI\nUwhsCNd5Yqfilvih8LKMgEBU4Xp7r8ASCZ+SpXkUPX+wRWewiGRKy34pUjH4\n9zuVWS8nxCEjQIwGag9zy5kman8bzMClFypPKxWvcjrSo4Lhxo4VwYOHxMNe\nsSgk\r\n=CoK6\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"698a9278145ef0b4e06e9c33d51051b9650c5b11","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.1f1ac7558.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.1f1ac7558.0_1577998434263_0.009463324147200192","host":"s3://npm-registry-packages"}},"5.0.0-canary.ec26e799c.0":{"name":"@material/auto-init","version":"5.0.0-canary.ec26e799c.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.ec26e799c.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"d08d5b1290fe38923e0c148954fa24992ac1584e","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.ec26e799c.0.tgz","fileCount":14,"integrity":"sha512-OXPQ0UFJO4i20jBvIbBB8IBITHKqur4whupuU/UkQhKgl4045ke+sBKqtPFrLjbP9f6JUxSJY84bzr4F1BOHCg==","signatures":[{"sig":"MEUCIBMo5JjaMG5R/LZzUP5es4OSu6mpugLLscMB5xN2ABP8AiEAthOvFlebDNUhoR5T+ik0XmtHotaBYCN+7lmKSCkkGco=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeDmOqCRA9TVsSAnZWagAA+SEP/itFrWY3+HfOZhTU18sQ\nn7qIdmXKuegIMEXrdEH2JOxdfUpJLTJtmPQx2blb+T0ffVmCY+Z2Gzu/b8l1\nV/7GUg3FZ8roUx8nI7u9RNg+ffF41icozuKU3Z+K+ZNtR9HF4Pz7adcB7zYQ\nHtJu/0fUFv4RHTVBlBhSH/FeMNmQYMqF0kQbDBEn9kRAdssdS9tYtDgGZ3p8\na5wUbsM0PikxxNZ72oeE2zzy/6Mj86AiAae+tIJTB/zJVeCrH82sVTzsnIlk\nUQrEqOlbOsJkJTn2Ws4Ic9/98nAh5V2vwZnPke76jat1d1M3zfzIJM5n31oN\nB7H01wZGLNEb7rJ7fdXhf2ut60flX1BszJrM1Hbm+iUEZRkYwiH5BQL28OA2\nkB8bKFCxZGcxSDuHutHbAkQfU/zyXlaCFP6EhqT4xt5PNadxuo20Hgux2/K+\nBIeK8pQlxnwJFFPVnOvSkXNgkqtXWPQfHVAEVKCCeWq5Y5jrbWx3AE/e+JnE\n6qeCxbxhB1lY0Q1KMyCq3CbNwDDylDJalLhHh2R9V2HBVNMdh9I/RHUVaKs5\ne5wt7UqSLkiSJSTCMHaQH2Hb3EdTGtx/HSMJRd3xXu9RTh3we+tVKXBz60Yj\n0MQxRVfJTJWOGk8fj5Rv5EEm7a/i/Do9sIkz1vRK+a46KYt9pvTrcKXGpoFK\nRpld\r\n=l3jk\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"813829c13087aa9fccac08bcbdda0ffddacaebeb","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.ec26e799c.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.ec26e799c.0_1578001322291_0.33911923379726083","host":"s3://npm-registry-packages"}},"5.0.0-canary.0a40ced40.0":{"name":"@material/auto-init","version":"5.0.0-canary.0a40ced40.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.0a40ced40.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"e05df5674b53d230d2aeb01845d56e1fdf45649a","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.0a40ced40.0.tgz","fileCount":14,"integrity":"sha512-A8CJ/15P+YevJXmx6gZCRnAaXmKjKwkUorgH5IX/XG0xcRH1mloXouFcGgz8eIBJBeifI5qa7VXzu6IPDzD1wg==","signatures":[{"sig":"MEQCIByy2tTK05okXC8+sZ+rtWme9goBBuFfp9K1YohHrmmJAiBK4tW8vZsEllu1FMymkH3yl077ROsJ9gBZJRCKzgfQrA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeD3UtCRA9TVsSAnZWagAA0cQP/2u2FlhklBLoPIrUkhHq\n/tjoZS55x3a02J6xKmh5fDWDeKA18YyzWz1yj92LOhash7FGotIkXGw4yWHD\n5C6TOWFADjbean+SNjQOvTVW6VAyKqL5eUKvSK7mNXGVJ7QjpfSrbuq+Sww1\nWLtn+16PLpeUmjt4zdeBG6e9l3Hnlvn2p1A5OPAeinT9f7DopYRq6NF/sY7v\n2KkKPhEfTMNTf8F1oK7xjvCczNCsG2LghtUg1RKmjDJkGgPV9qrigowUUbXP\nbJ+0e6fYAm/VaI+TvKfYEKeBp8c/LRry6+FD62DyWgBdbnOQnripnG9skNpO\n/pbaqdjXPXWJRiDGFY0oU98AF3NfaA9bjxHuAZs9qK+qu2PKKtMrYAniCb/9\naAFoi2089WxkedvsNLwkNHYbgxgphJTHZPWk3hF/t2WIcTKSmV3p5j69NRcw\nQz6pR3wJ5ZSyMQpwe6aiyIgGZB+bz6DG9RZd/7IFRAy8yforYBzolbwArbRB\naxYqKM150VZK1Y9hgAXdSX0L7ArmMq3o3SB7D/hmYWdTk1Ra4vCXbBRTx8HQ\neqifLACSNzhaDXQ4PFj9i538HEGBGLOK/be5FKEjnvSAljPop9WOvfyIJoFZ\n7+5yaJprLBGu/X4t+aW3DQ8pulhvP1uWNN6a+yflRob1UVtz3jYcVnwO3uk7\nh8M0\r\n=JvVu\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"dcddd5ac583b29d0fffe1a54b6f634f6b90fa44c","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.0a40ced40.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.0a40ced40.0_1578071341044_0.4505856698699515","host":"s3://npm-registry-packages"}},"5.0.0-canary.3adf84899.0":{"name":"@material/auto-init","version":"5.0.0-canary.3adf84899.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.3adf84899.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"7a1630bbaa20a24c6c9ee80cf51f92e23e8003b6","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.3adf84899.0.tgz","fileCount":14,"integrity":"sha512-lf964Nobkx2kjTDBIqV1Nw6gZtvtu+ioHM/hP0Pogs6+HSONkLqADT/nccYGLc0Qo8US5rTjLk3sMingsIxUcw==","signatures":[{"sig":"MEUCIBNHWFGhKP/I8uzmUvsYBc0CPhmSth1tQKJSOiDhXLDpAiEAvMF+bCjJKqmBZz80x/Rd3H1DMNRx6fiQop+T0nVL8qA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeD4ZKCRA9TVsSAnZWagAASFwP/RaDIGEgyOAQpHPHAkTo\nw60UidITAQqzQNXpqO9oIX21aVxRDVtrKowCcp9PDOTnBKbJJaDElPsFssv7\nXlxdWwQlsZr7krV5v+rtpzn0NwCM1+N7N3RSC8HTTEI3Paiq6WAhFwdEQq9K\nIYXfKvns5tIvJfSn2ht6/GbGz+AH9roz4epsIOwn6E8Xmcd14BPODCBi9pUE\nYuZOynWGc43ldjuofzDd3WRXrbDSSByetaDroVQ4OCo6IY9qY2lePwlU+rvS\nL7TX6SOn5EnxbqQG48iCMQTVezHGcDMeFEv/KHCg2Fx22/0lvob8D8rL58q6\nB8YwEFc01HOv3QeYzgmLEaLKCtso3uHYyJnanxGm5rDDzo/pycqLlSGV2VRV\n6sc7yPvOBZqcBO3ykZYKvobw+IAokZa4ML/IsOCz/PufOwnCVpaq1AzohNON\n6gdpA+XXfoBkBaLbKmPUnt+CaCPxF+Jn0ude8tYVfbCtngdKS/n9QoXzlYh6\n/tjmvrlc0GDVS5xDvbiCYTSZKWQGgGdO/4P4WyxP2DQimP8cZ9FWq6WXLu5+\nKkiNKBDpuDWoUDrtqvkfTUNN9OHC5Nt7wgnn34/1wLi2V9dzuQSBtOl77yWU\nWeqHqEujIK3vBvG/Rz344EUm57kzccrOX8uwU6evPyBmhr3aJUj26olz7k5r\nOlh6\r\n=UKaE\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"9f20ea5e081bb781aeb0d66d6db6a0ea7a0f5619","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.3adf84899.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.3adf84899.0_1578075721634_0.7142985640129538","host":"s3://npm-registry-packages"}},"5.0.0-canary.0d42ee650.0":{"name":"@material/auto-init","version":"5.0.0-canary.0d42ee650.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.0d42ee650.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"ec84abf97a7429829653d7e2ce6f28a8f01fa0c7","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.0d42ee650.0.tgz","fileCount":14,"integrity":"sha512-P08xGMdVyuyJKBBmaK40puiQRhWeZ/MWDgBSPEzq4wmQW/d04OKb4cEOSV+k/vs40ziWrGwxu6je8pTpg+cquQ==","signatures":[{"sig":"MEYCIQDzeSpe/4xBkcf1p4PU4fX09LGJa3TSDsE7/Cp7xj07mAIhAPtTuQ7iLKfX7jxT2fsH6YFP9adIvyA2ogkvV54CVTHY","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeD7PnCRA9TVsSAnZWagAAuPEP/1ulZTWutrNXPJeDQ2b3\na1ZqgARVS1Qp7AzwWDaJlkrDDTsQTLk1uT8QW3gVqmvhis2ceDRj29ykqIsW\nF2aMq3/M6zLcwoqXt+oCUTFOYsKXEJ3mVji4tgOzAhK0UEG7VDxtCCKV2LLV\nukFX+ufqAhx8I1CWNzkUq180DhpEiEmGns4xVXERhNhLxykfW7TQ8fcPVEqe\n3KxjN/GV4BVFIpijSXnDJvQrblH/oibxcC/4TP0MXCv7EkEreOC+XXuv5Shv\ns/sxirS/nSulfTFNAC7cvtGjuJPLzcCraaaDENmPyn8dIqeKTCoug4z9t1Ry\nKj6NScvvYjYyZXuRmEwuAItHXdxR8McEJnKriDLwfIp6QV2td5M6KkDb9hHc\nPuvD9Exb+zldf0w0p3tFN1b/C3S8qy104+ZO/kOB4UxS8gexf8xUtmI7X0Ro\nZXjHJtsDb4kBKIZrDrsUG/N9Iqera3Q0Uev3HVAbUgXDXPu982Gl0QvLGXUJ\nR8BiNVdfDkAZOPWVqOaL3nuK3Pvja3ysWXop80ak4dZaltgJad0XoeSrcfxK\nnxJMkAx+KuLWR9Vy7orrBA0JoEdQqoE6+8XpszlRS//vujSd5cdM4lk+7JP6\nhxJrlRl39EnxyS1nnAjZWJoD3l8mVyXinN6sw/eh+jUIHtXrBWl1BwOiGjaY\nd3GN\r\n=+sb+\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"184f253632333982c2b642e450e6e98c9703fe85","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.0d42ee650.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.0d42ee650.0_1578087399159_0.053064617419732896","host":"s3://npm-registry-packages"}},"5.0.0-canary.7be9e4a04.0":{"name":"@material/auto-init","version":"5.0.0-canary.7be9e4a04.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.7be9e4a04.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"b3325e9f45b2a94adcc0833eb5e0c4ea36d09675","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.7be9e4a04.0.tgz","fileCount":14,"integrity":"sha512-uXbbWvdze6Vu2xnA6eyVUX/HLOpQsuwp9Uag4F9LUQOkf9ZnBIczwc/aqxuRMqxdlPJjW+UpcIxDYoNttdqIwA==","signatures":[{"sig":"MEQCIAiUHGiM+mv5Ii+GEqjGYU0lCTYzQTT+7xvGhcV6EwG7AiBE8JPwwcm5GgP0qkvDXPty9Jezv6TKNuB/e1GvfK/gBw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeE2iACRA9TVsSAnZWagAAeoMP/06BvNwNbH0/2BkB1Utn\nSSQ7AFdE7G1aLA22Amkudfn7573GnYWI8WkToE4qi9hgcmRJc572hcJEdwMR\npFimXpgXrUIHUSkgzFWrre9gSX/JVZnt2MfKzn/2Ktkd1oE33tP0Ao5j4roB\ncRylZ5rYzCtT2Bb5FaemXN/Ota/8Ppv53u+IlNJzpvb8aMP/szuGtXx5ty32\nDa0RC675Yvlj5cvreZHcd5n5A966yae/17W6whbWTz/Fj03EcP4VOZIOGxLp\n8imy4nwnxSx+QIcrZUihGNJbsT1PRmmEJ/1/BH8ky2Kk8iZFWBPXZVLDz6jR\nRZBukbyxNG4LoYbhFPrZVYXa0xKuqIY6VSNj4pFytGiCVMCtceB0CKZNYueE\nHnW4fPHhLRAOYIbU/WJQrlvCalabKt9+VeudKrmbDkVeo+BHqRDFYPA+kE4K\nOzY733OLAFwWNTt6lY2pLWUuuj+NeXFXm9p+axM7oOH7jUimt7OE+4cpvsgV\nE8wgMFqXLCYgQ6ces5dxp/0XCznhdzStqgMqscJYVx5zkgzt1u55phmc3G5b\n6haQXTVLHILjnVYJuTSgTxxRZNsA101tJl9saULyp/RwtmfnK7ZuixorgYxU\nDJXMmhyUtJEcXnFhX80RpvO+eEQprbehGyOCLTA7Ih1nuhdtbaE6KPCCTiTz\nX90B\r\n=0hzI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"ddc1335b46dfbc2c77bc767ace9e68247f9f9db8","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.7be9e4a04.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.7be9e4a04.0_1578330239716_0.009761535512134767","host":"s3://npm-registry-packages"}},"5.0.0-canary.847dd1ada.0":{"name":"@material/auto-init","version":"5.0.0-canary.847dd1ada.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.847dd1ada.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"b760641b09bfd551927085d80b6ce3dde6b12757","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.847dd1ada.0.tgz","fileCount":14,"integrity":"sha512-U0LIdJeFUZ8MUvxhE3hRh3X3k5WSXkRppNfLhdoUYmpkAl982wKuDrmcoyrXst3XVcHcbZ2HIHr6fNTOJ/7fmQ==","signatures":[{"sig":"MEUCIQCS4Ps8Q8yT/re5U9xEx067CZ5znhpe+UIsdgShx2nKLQIgFYDlFaqQm1AESXYCok2GNdaOatqcUd+tokcxKGRcHgw=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeE4nBCRA9TVsSAnZWagAAbWcQAIIFnSnTZvXYAQLXLU1k\nYy8n69mCNQBAhZGYMHA+ah6dhSAFJ4qctsLmDMi4+uPZMqkBoDmRAmnrYtUN\noLtDCYwtMs8D5BQFctNlPdTfITa4EqufZ12RkhReXY7BQct1EvYYqNk0a5Un\nr/Laa9TLi4n3sScByWeHCBj1K4qLJYSx7MkZDIO4O5cZfsndUscfhQeQDoo/\nFT++jowXX4IIK8ZsQYmQg+IV1icNTvh+RAMF2fRD6rVNf1+rAKV2v9cL6cqk\nf4bk1U3EhS/Rdu9e0yhv6TVFMRKKK1jt57T+q1bE3oz+4xmg4dKAYv7tbtmz\ntIv/HUgyayZyl4EBTqoHMmiKt2DPKWsGq4xVNLBum0B56w0qQZfxFhY7rAF/\nhym7c+Q5y2plr3CgsqiXz2HpXvlNAHaGQgNyBEVfil7LZWfn5LfKkC4+VyGZ\nC2UC6lXBebao54PLPBxPv9LA9KgqVopB62WoeR49M7/HTcBu/yGCU3rYPlwv\nOmYOjxrk6W/INsQVzOHW/H6B93wOmSoN/HpHM4s4l2GFjOoL6jtlb3Wc4SUY\nj/puBIb3eH/XQq+0YjENHlAXCrfxFMUSqJXynB4NPujsxhsabpmxNz2giANY\ngyqD6jQE2gQfhto7PVN5oi+m5tR6W7WXH28siZxLwpNPbPpZUrrhieQqJWn7\na680\r\n=tKF7\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"cccb6b13f05f64e22210548991ad471df3de97f4","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.847dd1ada.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.847dd1ada.0_1578338752838_0.3769880430038326","host":"s3://npm-registry-packages"}},"5.0.0-canary.39df7e5df.0":{"name":"@material/auto-init","version":"5.0.0-canary.39df7e5df.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.39df7e5df.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"ef3d5b193301df3166fb6b80bc5f92337ccfe3ec","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.39df7e5df.0.tgz","fileCount":14,"integrity":"sha512-P+tzITb2+Ldt6htcREBBPAaV4/fNk4Qb2KCG87vtheyD1hdQcG9yNQU7rNZFsQw4QUA+zuuDDDUZCy4c/+js1w==","signatures":[{"sig":"MEUCIQC/plHJGgbKy0fJxRNwqoFnFjbe7o5SdlYyhFXL7HPHkQIgOjq/vUQq4Gj1KoNOvq632Kmzvd8/SWTxv955GquLUb4=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeE9brCRA9TVsSAnZWagAA5u4P/04/Nb9LLeU9gP03Xqth\nwD0zCQ1Tmx0K1vptHZC+tGCNPv06oLMJYxI+tcOiB5N1N655cqhpgReAhbyG\nh+ymZtY8zZIMdOqVDY8ET2CHLuqccdRCFvfucw0DpIWSZKOFHQNiofU1VuQD\nKMuDGAaXzfgtTUwQ2LqJCSTrZe58WT1jU9nB7xWZRKQtFnUj4wicykDUBtFl\nMv+TDNiewRMPSBRip0EDOrtTshxOLCAehd1tpbmb2WW67leOn5m8KPuo/eLj\nJuW2Ic9Y3kfZXoiAfITyyb6WDRoDUkTAup8sVKs2dy1QZzoBcyd+0q6GdaCG\n7rGX+4pC4SZUBKvs/Hf7n75quYSMC8Aqi9aV2Jl6OKGEHZBAQ6f8QPt/7mqJ\nJslnGGiPlDsZN4IlAN+Mq/Uc/ZNKJ6fkQzoVZZc+8t98qL9QseR3DNJMRQuK\npZLFBqpKwTwGp3SedTdALBBWspuy9cuzz9o9jjWCZK//scbTpkTYaomexhwO\nvmKQMU2c9ijkYAcswES6n1OBo/xALbaUMfs5PlFXxOvnEXVJ72GCgHZGV0ot\nyANtSUfeFKERm6pwekE5fRN2R5CIYA3A5PR2ug52WPc3UNIywF8q676NpTVU\nZzaCYlPK+SH7BpFMcXKJH2LyEo9ZTSTcrp8R39YVWItFEyq6tbhivVpAprxA\nO3Sk\r\n=Ap11\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"a6995715f8fc80d9a20e6b8ea90e80f4906ca595","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.39df7e5df.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.39df7e5df.0_1578358507131_0.3417780288212995","host":"s3://npm-registry-packages"}},"5.0.0-canary.f1a2581ab.0":{"name":"@material/auto-init","version":"5.0.0-canary.f1a2581ab.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.f1a2581ab.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"aa92e763d682ab42c9fdfd88cc3243af16d0c34e","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.f1a2581ab.0.tgz","fileCount":14,"integrity":"sha512-s8XKx3RrdBi0yi72UKmNwNLWYkw15fC+0prKZDeOi62adZgrS4oGt+0dhMixR03Pm3VW1KRJ9OR2FBuB2VywUw==","signatures":[{"sig":"MEUCIQDeYX+MCJpaYy1lF2UjMw5gWuHU1sxIuSiBdCZj9tfzXgIgUJtXxL6awd2fYrPqx1GWLqYv6v1QgxuDxcpm5iIhi3Q=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFJy/CRA9TVsSAnZWagAAQIAP/1f4eBcNnxjhCPjxBgM/\njeOVHCmEVwJcVdFq3uh1mGHb74US1F0F2mZrauWeykr+Oivefe0dFN8FVE6X\nBiPkYxe18fGKUVk+/hV04MwzNYAl1NfHpwlVtFWEa46D7nT4c83HNrJmrUzn\n5eqCQP7hq60ZpxzsmXl64ApiCiklitl4al/GzqttKBdnjtxXYxMsTCj5hcKI\n3e74UjPGObUW3gf3j8F0H0LVPxDWgdZVd+sPO4C017JkY01WQnBO1yz2Gy1U\nImY5QAGM6OJyKvCaZbu78Ka0pkg1hCMuata+rV7bRvaxd2vmyai6+RbPgpk7\nDD6FotlNpMgN8R4aAOy29BUIJuP2Y+Ud3hrvh6AJDiCVyF8KwfyQzr744UsK\nOxSwUh74+NxhnlH5XNCpAIw+WlDdMgB/urnEHyVBrXe9U/9nAxETgXK1sGfX\nHanmg55uT0sWWKYIvTIrAx1RZWT2V6Vl8LtaKeSKwRRW2IfIS4Q2SFKqsu5Q\nJLx2QJSsqMrtx5N2JjkcalEr/CAzf7ckAD44VywycvZ+J/56JWg38KMY3twK\nMEIwvvUKh0McmHUrOxgpUQe3vUrnMG0NSUE2KFD/yXT7wzCb9DW2u9x7zQ6H\nPBpJsX2ASTgR+tnZIBVM+xWwgQdy5VGZym4ght/wlt8gd0O4sYbkYJbDwZ2w\nWfwv\r\n=F+dn\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"ae69ee79a4a22a7695be055fc67e5b974c2b989f","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.f1a2581ab.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.f1a2581ab.0_1578409150916_0.7458686551182803","host":"s3://npm-registry-packages"}},"5.0.0-canary.7c7ddf347.0":{"name":"@material/auto-init","version":"5.0.0-canary.7c7ddf347.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.7c7ddf347.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"1df5cc4be8bc602ae79d79bb75da7a65dd45f20d","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.7c7ddf347.0.tgz","fileCount":14,"integrity":"sha512-qmxEgFj3QhZeaQQsuVOMvvzek2KadMBSY1VAcLS8/ERjV3pEmyo6KpOmAH41APY++UHOIDYbuEcP4gnV9lEUYQ==","signatures":[{"sig":"MEUCIQD97wyL8JRNwHdDyx8+X1z00FB7+SPk6dSqHO3UiaIYTgIgadZTWBFJ4XYH9rmmEEnA9n5XNeiJvG31yet0apTkEX4=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFKCCCRA9TVsSAnZWagAAu2IP/064NwpKaB5bnDPD6ror\ntawY3bankZuisoZPUHxROVimBIQ4SXbF6Nsbym+6zJ43yu0CY06CWMj3wUvL\nR0vRFynZIcQmMSn2k+qSD2gbUenw1bHNf3cMeYulrQKH9Nc9AnapC/V0sbi2\n5fRSk6MvTz7HyphIw3QnzOdp+v9KQ9IUVHuKepMVARauKqRwdSS6PZM48+Vd\ndjjQyHmrdpcF2XvbDYGYB2tFynMCgctNigFChIBlzoDkFTf1kHh3ncuZwio+\nnzzKy7+B4Exb/FWGjqVTkUBUuD7x+rS22nm23lAorLmge+tLjAUJPamoXshx\ncqLwYcRKl8+6ooVQ2n7rgLmfb18bAupkMOieEMswpZ+ZaeKiK1q+2P5Jpwd6\nJLLt3xAv77eyYFMr8KmcXGxduA6GH9CPREieTKWyYz9rcuWK8GWzxrkudy+8\nLAZefuVEFxjlArwic1RvnuM0+vcsjDNhBNiTm8UqDLydO7Jx1Qbf+x52SlnB\n/N1lMR2wQ0G49RKa9CfUDC5z5kjGPSMyp8XvqFOgeStopLpXuSkfqELBXiW/\ngLv4pqG9DHkZ4+dGIobyUln3OHJuLU2sXtW3+U0GSShUdHl554xj7cqkzPCO\nSucOAHrwWAnpBwhPgxjKMVvmfVuo/nHoISLuj4MPbIZ0fiSbqLbXI+h7eeVo\nuGE9\r\n=RZOo\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"940ae7448647ebd59a16a94b84c479f3f7bba9b6","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.7c7ddf347.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.7c7ddf347.0_1578410113610_0.9812863338682194","host":"s3://npm-registry-packages"}},"5.0.0-canary.a1c84d4b5.0":{"name":"@material/auto-init","version":"5.0.0-canary.a1c84d4b5.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.a1c84d4b5.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"3a5f5f1fd5e30d880d4f8ce7c174c654998bae8b","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.a1c84d4b5.0.tgz","fileCount":14,"integrity":"sha512-MeiiY+jlZmg8aNI1Pi2ZyG8y/zFbFvLf7t5Xgorj0PCrqzQO5ex59YOgPSYkbbCejCbW5TuMOTTeHPFWV7315g==","signatures":[{"sig":"MEYCIQD9D40AF6W3VFn/Pf4TKwsgjpRyh9WMrT6F6L4vcSfNaQIhAMFcBSiOCXzoCoByAGcQqfU7tS961zXpa/8s/4dQog2H","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFMliCRA9TVsSAnZWagAAO/0QAJ7+vuaUEQHxpkJ9VjbY\nZvK0B1v+X+IRgpmQYME8onrfnBZp7lFYzFUuMZUQPdu/U3nCdSqAowIhRpZU\nxHFy5rWzBVnrNSSXvw95EkgU7EC7OialqwGtUNbv620Y78+xvzzm4XIrv15z\nLZ3oE3VDTugvgkf2O6DMT4NdZ2W0K1mO7Ephjs7wyanjEBYlAhklCQTsQamx\nIElJtwK/URfrPXyWOa2rULZh/SDbVTYmjNNIy/8Sy9OsBDho7VaIo0KJD3K6\nrdhQzhbd7LGGzhj9CIRg5DruseQQyPLFTPeQXYycwRz4xBHSIKjyiDWMboo7\nBjfOaE4fti90Kq0U2OSVaXpqgauAhbf7pzrP9QjERQkiAznPDSwgaleM+6up\nEIpZistggLtkNbF6YuQT/cNBLyaLqXronNtmz2/DczLgDtTHbOF4qiG72cfA\nCWMF5DK8bK1D4Pjpavgv6ApmX5phvB6D1i2y+z3gBnan6jtkE8VFHZo0Txce\nYAtq/nOKE93FSdD5btH1VzQTaZivfx9ZjVNGi9AVlgw1bK0UlL4zOaf2jInp\nrsPeAJf+k2XlqKDgkvGJcQ4rTpjRAR99u3K76PSC1kBQ1JaDhxZSYStBlKDz\nuORX7FpF5qm1Hp8T2QxjqSlFNTC/FsvprcN+tbQ0N0SRcH52E80EwdMNNQbD\ngt7s\r\n=b2h0\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"5ec624a1b571d87d94d5187056a0b6db214d229f","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.a1c84d4b5.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.a1c84d4b5.0_1578420578407_0.8614708836239824","host":"s3://npm-registry-packages"}},"5.0.0-canary.ec9f16578.0":{"name":"@material/auto-init","version":"5.0.0-canary.ec9f16578.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.ec9f16578.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"bdb8041c8fe630f2ba8f23df419fba7e54cfbff1","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.ec9f16578.0.tgz","fileCount":14,"integrity":"sha512-+4zISKJX/ckeTWGDMKAykN/HQGQWkzKi14a7CHpctmxYtdzNVqDqnuf2kp+HA2m/YONmymvGYkOSU32knM86Kg==","signatures":[{"sig":"MEUCIQCzFiWwjmcE1v8uBwbz33l2xbgTg5JhYbk8ULVA41UV2gIgWGptPdfHJ1/9JSx/lnZotd9Ta/JxscWYlX/PoNX+ow0=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFN5dCRA9TVsSAnZWagAAlVAQAJo8TDILAvsNewjAU3Qe\n46IbNqq9pgAkXZE8XiBGW4VDy6BX3lBlkruh+ppYF9pDr7GwAYvxuyNrTaVD\nf3QbjSyHpCMOfncT7ONC/LJnhnTIs6aU00b7ilTgcVSUY5gldwwVSwBsh6Aq\n8cwcjo++lgcY/YTHMRNcZXsaE0uRuf928Q8zIEZtst+akj9Bmjd3s3qwM/z3\nzJ37uv43HEd72xqGJykTGd2W0JMefVVbQjn5yipGsoBA2T0hcWgZQmMJ8hB5\n52bfmcl61eX5K3UMIb56hNPTIkLAySNa7P5AtWcjrwc0bvKgXw95eWN5XOwM\ns8fiEa+3cIgYTaWJBqDh69JNNl5VcBhGoYgRO5aNzhLxzZrJr6blmMP03/xN\nh84CKcd1ul04DnqsYNWrn62+c6pgbD5j4hstTZZuGZEWN8SGvOk0f4om32GX\nmGijX9La2iC9VzFGfnMkqHwU2Y52N4TXAHGu+ZKKKPlftnqpGOm/ieqU+NoL\nfzMEy7qmJRR11tP1zoVVmhNYwG+lo02k2pMVx9Bj85pGe6kvi8EyWiSgmiyU\nhVhckMa6KAouACJWj17gmqSPz4d8+DLILp3nP9d0ZrLqIORkHZmhS5ZRffiA\nnekW9FK7uCEsifwmXOhzhHzFE6idA+nkQTPtKPCEOiPfPhFDyGjiEeRD8zRQ\n8qWg\r\n=HWXi\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"23103621e66342865b8700c5948ef9134fa8d1fb","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.ec9f16578.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.ec9f16578.0_1578425948961_0.5442240988087474","host":"s3://npm-registry-packages"}},"5.0.0-canary.b602226ce.0":{"name":"@material/auto-init","version":"5.0.0-canary.b602226ce.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.b602226ce.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"0d0e508a422597daedabaa526e486da5ba4f9bcc","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.b602226ce.0.tgz","fileCount":14,"integrity":"sha512-++cNuvLyWirIBkapxKtXHIr1lfA6uQmSH/dEXbVzkMpUrqLfU8hssczRRGLwojGGUIIK/OF8eLA7eiNHhV2lmg==","signatures":[{"sig":"MEUCIQCo8KYxdMQ/Fy0CfQFkP7VAlPZbg3rsMPRyBcEy+hpZqQIgKMXSKGNQog3Qpvq53UMRaPDXZ3a6gazXrH6kskVEhC8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFOa8CRA9TVsSAnZWagAAuksP/1rEMNs2cT7Tblq00ibj\nMSXlsfxuK6B/NE38k21Z/kf07Vnb3bXvt6lphZ+vxZNbcoTg4tDz4uzLG78y\n9pYDrl33dttTKrlLMWW6lguTG1FgQ34ObcJPL1OmixXnbKCS300eOqW1QxpJ\n3nfwavv33V5n16vdUTgxrzcV4vSMLxvqklx2WPXuh/7HBC+VpGG0ywTyC7Gy\nH8nrtSDKIsKU78oAVc91qkTCqq4VfKZkOZIP4d9Qnd3CLbTpqlw3nDL7yOwJ\nJcXEIOMj5lmtijuztx9EkPhsBjv6iEZrNLH4UWTtH/7GoXLoShoMoHqaBI3j\nfqQmxw8xCwtYRyu0283QNvUReHTrUMyGQ64rI+upCOxAzprnhiYkztD4jB32\nDjxdquon2vRqw5mnVgJO92j5a9Wt5oAHJUN2N9pvQs+v0cB0rDs41qFj7rLr\n2gy5Gxr688egkfoMoS4ofqtSZRPx3oiRspYTbWi2KPHX3ZykJmdWZpvrIxds\neT7UVauJgK6Ib+35sZPdNGUzbQfN8clcKuUc5LXUuTrETCzem12a0HyTz0cV\nZOuQepWpuBPrQPmjMh3g9dggi4QPXT7jF3CvdY4m1YGTavxfTWO3oB5whgWY\n1+nPF87ybi81NxA7EwJL42Qpws+4THGH9o2ze0O9QmzkjnOaM/wo1b0rOE1S\n/SCG\r\n=Bvwo\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"de0d35ec6a5285ea0c12a54a6e35051ccd0aac1e","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.b602226ce.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.b602226ce.0_1578428092434_0.04683991964912071","host":"s3://npm-registry-packages"}},"5.0.0-canary.b2d2dc08c.0":{"name":"@material/auto-init","version":"5.0.0-canary.b2d2dc08c.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.b2d2dc08c.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"2af483556f48f05b363fdcdf0f0ee3c37b78bc10","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.b2d2dc08c.0.tgz","fileCount":14,"integrity":"sha512-4xfO94AA/YqFvUCP+EluiFD9gjyPYBsC6u4qsDob2WLhq+nBGgBl1Dq6ZQjLkxIezLI8NsNeZCP8gUYgKdIfxw==","signatures":[{"sig":"MEUCIQDKmJHT2nKlVIMbBdQQfRLfhXdwi2MbrZ2qFAUMkMXYagIgCqT3QEgtBy60o2VClh+yTSlNxtDJUyZsp/JbNZd/j5w=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFPdQCRA9TVsSAnZWagAA8fwP/iNLD+RmSnbIe+ByI0M+\npkl38gXpEAdoTxO7T9f41ZAtc+e//MqD5GBYN76IS6hzST2RCHDVic7zhH7a\nHHJ/n8PLmpBUfKtOyjP5qVuelcKcVQ/BcgmeU5SS1UsS1pHqKGjhHakwfd2/\nkCKjn2cqJvGjZAgJQW0i/yxzF0NBXSnIub6KC0AuiA5KAvMl2SNLdqc9ZQTE\nvU5WDY65H3evDnAvmzAiSjLAPSPLkuDf7dtQY4O5XDNNxW9YD9sh7BPfDZrA\nFX6o1x7wyeO3+z2rarG3K/XERnOlwYDT0Gv1qHqWsHilUGV+MHUCqPYzvLKz\nRgasCA60SjXDKFivKgUv8UsAuNZRk8/6pYqJzppga9XHKI0BSRIIRHP3xESz\nB/uFfgEFY0+F0bHR6a0l+oNIi+1uGQ7YmcUDUxEQU4+74up46weMTJWxfnzC\nTwu06R3aWAMWLVjqj9x/VwrX9O4jehPJ1dPdp2+IiDNgUtzrhnsRlI6dRN1u\nS2t4G1k4ydr/1K8zxCOX8MEynLInqjSo7gHyePKplsxHCCW9mT1ouWc6lF4j\nzzkKVzYa5tiNbY2QQ1k7eVDGz+iMN7C7lQoD6+7mN++WbRDnphe4zWwDFzFX\nrECbIN5IJhFy99ByzYJFEe5WZzL9yiI3PBZK9/cg+LAD3L1TVTP5WEXJZGgj\neV6c\r\n=5Xi0\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"ec9aa1966e1f2e307207d815ccbe3f16750af94c","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.b2d2dc08c.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.b2d2dc08c.0_1578432335757_0.7364181071394598","host":"s3://npm-registry-packages"}},"5.0.0-canary.61f2d7580.0":{"name":"@material/auto-init","version":"5.0.0-canary.61f2d7580.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.61f2d7580.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"8de1700a3e4319572baad67cdf91599a347f84f7","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.61f2d7580.0.tgz","fileCount":14,"integrity":"sha512-AV6LEK9bbemoELkrX+gW0nIh+r7MybeR1bjjM2pIyp0PaATYkfhYSq7Lt+X+ZREFf/2jP0CTe7hCIePa7Ve73A==","signatures":[{"sig":"MEYCIQC+7xbPCPZVAF50T4B8MvyoPNpbc8c/MtO3xcQR/ZFVvAIhAI+p/ogS6oRUjto4+tC5Jf0c+EMivXhcGP7crYSYvgc6","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFPqFCRA9TVsSAnZWagAAsOEP/047zXybssKmBFGb4DEc\nGl7KTZKrFuZNt2ML9ECCAyNBWRCbxRq0cf7Uv3hyhlM01mvKwve6vM5F2xGL\nNkSpE+RyMQQGS0r/ea3MlijMsDhE9qy2rvoPYNluicywF11hOGnA0AFz5NN1\nbjOACHlEGm+K7ad+yLSglXwDsEqueGBZBtqsrW16bctPKWAOB21/eD0OxkrU\nXkqPQVxtBvIXSfzGvzwv0JCaAFjuDC+zgZkxJX1xBMoymLiCXwVOB1QuWWly\nJSLUSfpuB3uPlXNiZNiLGJK8NPKBykQTUhqRgOAOup+eIij3/jWST214MDvL\nGYXGl5vJH0QKcOsBQg6YbAtYJEVDC9ZKWB9xAfyT27vZYRVJ+Gud3blNMEeZ\n9ZnJI3tyAHCNBEJezDN/wwh4zwYhGfB1ag+7tTW5vlR8OmmmHwSHcHWo1TJf\nla9IW9pdxqFNsOgJi0JLIp33vUE6NPW2BcUw+V3n7rrG3UwRy0Ene6TxIj9a\n0Ak6oQ1jBjQQfqvvNt6gC+y+hW8ZgZ2IqAkdoudsyIoRRT4ADfVrwXf4px1U\ntIkZxo+OLFAmgyPJnavTwZtCgCtFcBMz3B3oFQ5eY5ZTJ8RFHczN9s3Lo0H0\n1oL4EXyjNKWWenr7pJPrqt67AN45oagSStFSeWUX0VLRQwPDOTDOH5uV31N5\n8nNU\r\n=Y62i\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"a826fac64c34ef89005bede280cad29c76346e55","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.61f2d7580.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.61f2d7580.0_1578433156903_0.27773607990676963","host":"s3://npm-registry-packages"}},"5.0.0-canary.d1be53a2e.0":{"name":"@material/auto-init","version":"5.0.0-canary.d1be53a2e.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.d1be53a2e.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"a3aff330e240253a7a79a8c92bdac54cc245d795","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.d1be53a2e.0.tgz","fileCount":14,"integrity":"sha512-qNWJMgt18mqIXZajhgSBrmmmDhx3WHPPRaaOycLtqk1DhYhErvitRBkoZZEFw8aESbrK8ff76YnhYpzcb81kRw==","signatures":[{"sig":"MEQCIDeWoAUsZp1d6FrCzoaQH4BVZkxPJ5FW/3CHgVm2cCz/AiA3ZIWG5FQ0HF30Nc01autRodBn84BuEPeIEwAYd+kwcQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFQM7CRA9TVsSAnZWagAAhxQP/2L2bngPuY6gQFzeDzPS\nppUrfzyLT1x13ZXnMBzpydwLm9luaE7vxuUu07+2rXvwY337WIOIcGUFmV5v\nvzn5VR3PTIsbZZgpJFCrGu+oyYGK4lx675mexo1TZKmd5XrJamlrWowBLDPb\nQSlcQRNAee8n7sCnOPS9iuapkZfRpT2yKlAPrFuquAVqQpNfU6Kq4iqOrdGZ\n/dyV3S5ZGZosoEj8kJsO7Jjh6qpySmwcPBOwhWa3M4ixjpZa2RWIsWr1H02S\noo8p2zq7+2dyQaYiyox1l2dn6cFzEfPyt/pt4Zu5vH9ahhTeacR6EkQYhrix\n4Fg6oAOV0DdU51cd5T9NAnTNg47dePk5VFrmiqYu7Ph0pDmfZ1oxa8amRi/Z\nhGgRVstrnHhZi+RIR2elVTksaz+ACwa4y2NwiQ0vPWbNfXM9cjsv4bpNLHlt\n7g9j0Gf6jw4UqrtGGiJTPvtgWzGpCe6z3R42bYkQdsqkfuJEvtBNkhyyLuKJ\nHY2GMkX6HoWIE9Lt1/ZnqLnF4JhaOamN7E9JdiFY6bpnN72DvhGai2OTjOla\nDxsB+9VjCOTKUbRtKalEua/llawT/kVNYeBigS0Y2pd1OQWobNw9aF+64TLn\nXt3YqVbE9A/zmwFwJfuzXMvCF5PlBi6JGBvbbsn5tMW1K3uEIOGr2gbqS1f/\nECDg\r\n=ie1p\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"5053f71f9a35d62630821c2c4084794f7bedf258","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.d1be53a2e.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.d1be53a2e.0_1578435386783_0.9246944012871425","host":"s3://npm-registry-packages"}},"5.0.0-canary.9b0d06e32.0":{"name":"@material/auto-init","version":"5.0.0-canary.9b0d06e32.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.9b0d06e32.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"f9a21bb0ea3047e1a2cdd81d333c4dab720257a1","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.9b0d06e32.0.tgz","fileCount":14,"integrity":"sha512-yIXuodEQe1rk9XmeOwJqnIEtT5pnxtTGpJKCz27hsQxkPIVx7XuIUYk2NSel6d9CYCBbTCD0LLX6k/w+/zI8XA==","signatures":[{"sig":"MEUCIQCF1pV5Z6601tPqs6x6tLyXYm9EUIaVw8EEal0864bviQIgSPdOiY8w0c6qglWGt5B9NB6SY69e0s3ufVIjvSZZVxM=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFQPQCRA9TVsSAnZWagAAgtkQAJctf51pgkc0yzUGAUt7\n4RrKJ7LfXfsG7ILcKZYtpv3wIH0rr4xUkC46/7Fqkuv0MhIXQOPhcVWscdKu\ndLK6VXVzNOxjiMn35j/q7mnJSqwR+cpezl/xGJIXODjUwzNadsx1ZwN3tayw\nvOtCTv9hm1/lX3tquOMFenGgnYk4v3YJNK14y3iBgC3cSWdpuN+xi8rq1PQA\njcNQuZHgAwcxD/vUTBlyKFUO1AbDxkEaDDR0JIDeLXKhtnWrkjKPD/tKgMZq\nW/Ehn/e9OvAym50sVTazFlI2Nb/idvnlzZFKyFW/WlbWApIUdi1yoXBczXDJ\nmg9LBZlIksIYArvft1MSjIdwI5Hw8ebY1NoV/+bXnWpqHokLhJJT1GOSS5AG\njKKe6xaKFJMkqbCecU5KwDXr1xZY8hHr/F2UqsXufq4OgnMZ/olezbYhT78J\nmC5qSTi471Kn247MY8LMmrOVlKgwxbv7UJZNr30ZuH4CHiNiT6FKyT+rUZzU\nPwka/i4babhXEnr/Ix0NfGzTJNqU8aWi5xjhoZi3O+whYQOin7j0dCPg7iiQ\nQcAQnwu9k0+tT+u8PKKLgDCFUQvtwu5CooDrfhuxIUpT+PN8lG9EhS/ptU01\n0avrpqPX2uSIS/piOn9cX+hCOUdtxXGVYcnAZIVnyD1pWkcmncokNDUtSFrx\nyhbr\r\n=LPPS\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"485fa4920288a2a37995f4c736a1d429de15e53e","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.9b0d06e32.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.9b0d06e32.0_1578435536371_0.7978773706714306","host":"s3://npm-registry-packages"}},"5.0.0-canary.730c807a0.0":{"name":"@material/auto-init","version":"5.0.0-canary.730c807a0.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.730c807a0.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"3756ffef9a2ffb40f15e023b3a13d40e2e17939d","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.730c807a0.0.tgz","fileCount":14,"integrity":"sha512-3VrTjYKD8FjK7hZCNNdbfY7JkbuVzcbCU3eRgiKIEXfXy5/0mLkTF9hIhfWlC9p9EGpSJ307uThQuBdnJdHKJg==","signatures":[{"sig":"MEQCIDpn57SHZKx6oCwXiiBWF077Zc/j4DzIBjRdEAyqzt9dAiAHPoLle6Ad9l4ochFqd9+z+1YFsRuo9S/vBlK+Y4iMsQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFQQxCRA9TVsSAnZWagAAfH8P/3TJvuF12uTDx3JkFEPY\nu89W01ipYSMkLTQDW1r4YA0loR+MzR7LKJvuUGcO87I7Os5P9JoxnIA4Q725\nqlaQ6mA98wjXUcWTMPjV6BaJMKhRLXcXkPY9y5UYEzFqqZ5IGwIUNlre8gtn\nDev22xArsPhYzvysIpT7iszr92Yh51OJ8/ZyIMatrSPGsMH19fTkXkMTBzyp\nVL++bVqTy2ynnY5atR//LDtldPADwoK/vylbMEGKliZ2uzMvsNzfZtHUkKhn\nFlW9EDAAgC8Nhe1cT3lk6MXZdjEffgJ6jdjYe4+4R7Vo2fPs/FtYOuBPPByb\nSB3BK7lUSKthk08APHEz2Quwbla1xCmZrKJKVXtpsLAKZqi/azEoJSArfhBR\nMFUawXmeeUdSPAhYhSjS+1Sx67tk8aP9d7JDHezEofxok9BHOBlYkXqq312h\neE31CZoUKFzmNq/ebIHD4vWKbECRvspkrIRoR0Mq2P+sbyLRmbTuIeNmvoxq\nz7IFrayqAaENvH9T8Z9mRCZwEi/2+LPUY36d+qGXvidjqFj1mFrBT23FHzpC\nB+75K4zN81Kusw2UuBbFteeZnfil/8seqRJK6ACgFOeIxMkCrnuTSsZuvbdy\nYOKsHXl6aCoTLHewH7oCP9cgvxJZ0+qEVar7noKy20yclBDuswQxoWRzqrRC\nhXag\r\n=WoeW\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"8860f1c513146b0f8c59a8c70750d1353e61feaf","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.730c807a0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.730c807a0.0_1578435633072_0.6816362411493981","host":"s3://npm-registry-packages"}},"5.0.0-canary.2213152cd.0":{"name":"@material/auto-init","version":"5.0.0-canary.2213152cd.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.2213152cd.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"6bce8f315b03fcd39dc436969b5f11bfc35e4b11","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.2213152cd.0.tgz","fileCount":14,"integrity":"sha512-Nzn43BQZa47dFv4gjAjE5jhNKIi6DEAlVr2qnlRoQnyo68c5lWVGgd5K3dkTVKd6398WcRDcJazLTnbzMJqDcg==","signatures":[{"sig":"MEYCIQD9GJclRM7pGyvmN8fhDD+B/N/rhgniTSyQASy8mgBkuQIhAN4Tb3TLbVjIzt4hiZanv6bNOBt9BiIgi+/E2zklFhqF","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFg+rCRA9TVsSAnZWagAALosP/ilzqT1RtIM3pfJgmwyk\nigUu7JTz/y23GYtU/c/Pri6kHf0yCZpNjUMxsAHAuQI6pv1YaS27SxKK6tyA\nAP4HeLQk1ejtBIXfQRhLswl+fr+3EwHdR3G5yx+oLJVI5A64wtKwps1gdF5b\nTuHehRj8UCcADjkNKgvEl+U/tZlKOUaRlUVqoywAzrSsm+K9mG+MC68npPyJ\nktccoMJ3ixVqWElajpv4iaIsQPcSewnQuJGQSfm422q3l3F6w4mNO2Su+Ufx\nyuRy0hKW42VieTkJ7/qbQn68TZuQnIvLDNY0UVf5QLMONGvelyy5fmq4E7rX\nNvE3DCx7IA2nZXDJssFqRK0qBFWMSBKuzHTbfmBg06+Nu9hUDcyvENL5Yovc\nc4ZQc1omKonW5P3FWm0dDK1smps0ZBmg6TKu7ABj+7U2ieMEYzkD4nWK2xP/\nXCyiWiyjbwkwy2txO+yPw7LoINXzBoylTLrty61Bl33VYVWuMShzE5nUm1qK\nkjYfXCP7cznMzeqK8W75G6kGNM2Z9uUibkQRzTWkgEKUXQc/GOjSUj+PNRda\n4GDrIv8vTRw1IkAjPDdctEiv7ttgWyiLfyMNLbC6p1FPSr+F7KswOaJLmmmV\nIRZvGCakhHoJ6jmYxflAV8X42BMjnxk5uwJn/55V692tP6+LdsdBghs7aAtT\nJRxO\r\n=1YPP\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"0a3677a82eb2000c085d0cab420c907dca8cf13a","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.2213152cd.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.2213152cd.0_1578504106807_0.07661724655209512","host":"s3://npm-registry-packages"}},"5.0.0-canary.5750f7169.0":{"name":"@material/auto-init","version":"5.0.0-canary.5750f7169.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.5750f7169.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"c4fce0e81538fa071b3ac527d2b906548f620ca7","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.5750f7169.0.tgz","fileCount":14,"integrity":"sha512-uY3Cbyohr6vjkHBzKNjB+F+WQtN+4y5Gwwi84VdYJm4wBBNeDClMbVQ1xAVlJK8oySofyAXEGuiwVA7O1qyiQA==","signatures":[{"sig":"MEQCICgUmoZ3ZzE19TozR/imgBZa38tGVjhBSvJk7/73pwYXAiBx5tPeroAaQkS6iSdcMyjWvMA8xJRtXJllrhNkrKkGiA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFhfGCRA9TVsSAnZWagAAeiIP/3bvRMHFf19MgVW2ebR4\nxm3io+BFG30DRu8H+kjEGrooERbpjS3C8WkL0QAJpQb96jbX4BWqrk+awL8T\ngKBalTeuwieD+izvUIGlClaGJIhSqEgEZUQae24ozzZO1EQftXNDTaRhuz1C\nxxFWDYpV7azCQJO8KtwT2V9SmqlIIjtaYoP9cq+wIHM9vL+qO/7QjbVcwutM\nOxLrFSlI5BXT4s+BV7wO9Iu+rfGl75uN0e/UPcv4Ua4cSMyd22TrEg/yNLW7\nAwUPXC0ooEHerdEapkCN4L2Fy3iJXC1LTg9C/F56nB3B2ZZ3N4YSLPP+E8jf\nvUUl11gS2pTb7nhGpzXInPzoVf2Uf4UjmcUrWzX3O4TUMrRno35BtD0MjRdh\nv4mrHKzCebj96FApVyhF2EcpREGAEKHK/jecNGea5yFPNk3lL7JuehTVFAjh\nwaVLV9q5sjEaIBlG7JrWRA9QvnURikDQqe4+3jQxnokiILV8EogmM16xuhBw\nlPs1Dlwso8zZhcJs3xpeRytQJjNcxM6GabGqjMp7QCtuGE0trd9DTe4T5+iJ\n5p2iMRoaaeMjXLSg7BFhQrMb5rRvxmPmTLr9/YTadmkdXuvjZBujVGOck620\nl4a1O9LVFVMVn/pxK25Xs2fDUAeKxk8ZeTHdYNzJ+mZPIqIo4KlZ4f5DmQt2\nwJkQ\r\n=OaQf\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"394a48c85aa714b74edbf6f2b4172e4b066f604f","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.5750f7169.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.5750f7169.0_1578506182116_0.35167608719059995","host":"s3://npm-registry-packages"}},"5.0.0-canary.f7abc7a43.0":{"name":"@material/auto-init","version":"5.0.0-canary.f7abc7a43.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.f7abc7a43.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"fb909c9b7346e186c9ecea5621e300d7de57f683","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.f7abc7a43.0.tgz","fileCount":14,"integrity":"sha512-pL4IHJsLSxQilIMP8VCszdo/gkzdO+dQQ3EFCZkMXwKy36+ZYFYI/x43p2xxCCgwFu/9qGjzhs5ahz31ylewog==","signatures":[{"sig":"MEYCIQDW1qYdOMQV2MxIrC0dKTIaCjnf9KItMWO/Yd7cu/Y6BAIhAPDSQpL4ctaf4Xx8GSb3LN59t3m/DWe8go4itOhv3Ayw","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFh8GCRA9TVsSAnZWagAAIe4P/iKHUq2dIbdXmjJD2cin\n8+ohjieFbE5+eeWPMSbmWN87BYc42ncuVlB4OM5IcJQoNnYlpajRfCt+aRvQ\nO8LWtNAERFH0YzvtJWazbud/biBiXatyzQSMaIWKrak1xtschcGKUoftPAvP\n1L2iWRPuE799LI1CL87TgsANaaEOTFQ5LgPkdDpry9526DAGJ1VBVFrM3x9a\n4QxCZ2sRs+EsB+3X6nmrEBI6fC0oIeW8EPggLfaqCUDGFWtFLZsk0njl7FDc\nf4D+EcDCJVKCqGCHfbKSYNL7wKzKrUEeQmkuStoAEr3RMqVx3UPKSU2H/AKk\nPDzc1bvy0zSX7equVq18GyksW1O9VNak1otAg5g1oqbAUZyjpQdWzXVqdxsj\n5PHAYi6t5ZP2nGFcQYJeCE8vH3dzLKILJjCzIqCnvyYIbcd/DEVbTDpxkh65\nc0VmFR+BVTPJrYc+PDpzNTnHcBDjlfO+dnl/IQIlJCtHOxdGPBZKTolXTdRB\nrx/aMZeCpH5y/+31mZyWKmjF07uX+ibRKbDBldAF8k2LmfDoRqRjaxa99ElE\novmEP1dthLipaL1+sIk7Q1pTEtzNSx6vjtvJemTM6SI0GUbCAmy9jlT9Qz7R\n/PqSRxJsptcb5TtVgz9jiHUm70JzOZ6NLuxM8DkCtRrt6ize8UkOe+RGcFUI\ns9ar\r\n=0Coa\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"f7431b4b45a3e410e9cbc1ae6abe69c3b00221c9","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.f7abc7a43.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.f7abc7a43.0_1578508038403_0.6749764892715489","host":"s3://npm-registry-packages"}},"5.0.0-canary.bf7b4a061.0":{"name":"@material/auto-init","version":"5.0.0-canary.bf7b4a061.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.bf7b4a061.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"4750190d9085c3b32a3f36737642e2fb3dc86157","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.bf7b4a061.0.tgz","fileCount":14,"integrity":"sha512-GX08cmaeBXaeNsYEmUljyeNOspTJPsPuPdeIXQOleSTf44uKJO8YXDVC3CM3KAVtzi51TYfiLoRvM/Ar8F25pA==","signatures":[{"sig":"MEUCIBKiPdk0mcWFn07YrTT0wv6Xiu6a9e5jqa+d3JjSTiDdAiEA+7jxVRqXPiE96/CW8P0Wa6uqb90DjnzuO4JZMuk+VvE=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFiJDCRA9TVsSAnZWagAAYboP/Amq69xC2j/adzMIHLo+\nh8Oouq/ioFhxX9ytn2WH2O5auOMcIS9tt7ifpfPRHRcFRrr2EvIpd2tazB5M\nMqMAM518JE2LC5Q+NUu8vaAYcp0pDSobatCnu1Fo1xBth+4JAsGrTb3Ikfaz\nMPJNN7v4yWSnQd0mhWZlFpLGnJ639FNj8Sxnvl3OLOYyBd6YsZhn+jmboBPh\nbzxjVXGLjNVu0igVOmLonMy+SIY1qrLkc+DINO+767HwrnxpvlbwgusKmjUB\nfzKhl9I5Ofj/lXW2qcWSzo028vTf9J86qG4XYGXjW+hmJ+BWLhVurI1cUF8d\nEdMKenvAYC/fHHbUgnEJE/OebEaDJ1D6j6YJuE7aNs71WFrgxzfLk4H4QmGf\nK92AYNWX2af5vkU9CKvkcurHeH+HDVvd9vEAv3ixWh1nM35zGuMBr6bVDyOw\nJ0YOcIypSeXdqguWsHQ6oCEq2cKjcVE3rtdhSA+rvevVQB0QDCUKngvlzCB5\n2L1SLVDywuvGq86NfBSIunYiRkIGAztPgL5PjBXaTw0/nmti719X0vaYfIXs\nioHbnvMWQuIp02H/UqxEDxCjep/lSwOPtUrKwKl12P3482T7/UxZo/qB7nRW\n5bMRbuhyUaz3MK3qbTMp7vz7w1jivMcusWLtcWy9MnOfu9v02Qx67NCHgM02\nWLG4\r\n=Ymdh\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"2cbac03ca7852ef897dec80561a01faa8b537228","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.bf7b4a061.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.bf7b4a061.0_1578508866523_0.22440522602293078","host":"s3://npm-registry-packages"}},"5.0.0-canary.784fa7903.0":{"name":"@material/auto-init","version":"5.0.0-canary.784fa7903.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.784fa7903.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"ecfc2f9edc07d382fb3a58e9483a4f2450097959","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.784fa7903.0.tgz","fileCount":14,"integrity":"sha512-DWVgqr46lYjXgrRauFELHK3ko2ZfjqiSiBDwH+kX4+vZ502DEPG5c5dBfiufhUxNojW3nWGOBJsFtkB2q/wjfw==","signatures":[{"sig":"MEYCIQCH76o490Zb3uYOT5p/Zlchk701/D17EgtQYidaEsRsXwIhAN3HJselXd2b6MmEYI/EPTlBRtGgU1Yz8T8BM1bJ+7To","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFikCCRA9TVsSAnZWagAAsQgP/R5XUKAzFo0/DRgMvTzj\npFijmNoIutQXzQVNNtJ1K+1EY5tG6MjmHdlRsLuyGXK9Cqy/9w7oguAaK+5N\nO2P32z+dDP6BXKFyl3B9612eCk5MDpqsh4LMUSddWaynDGgelFa+NBkwJAsR\ng1E/c2N0WVdjo+CLiqnpj+5A5fwSoJnJpsey1xwhyAvPRuboXLSNW7/GcqhE\n7L+presRYWN84iH/ixZcq78R/RtjVaFMN4qyEx0DKcfBg1DWAYG4lhEc7grY\nVp7zOQ0Yw3HaxPSv/6/8nZghFLmw9R/dWzuEJPQGqJrhC1jzmyO7ChxCeBj1\n6gXBbt0e1mwuNqdpm49JjtH5QfU6X3oqutqrXUsoHH0bT4xzPlpe41JIbA5e\n3nRj7uWdLv3moXCuJo4e3QFyQr3aKiFPh2z+oUQabM2gensDGb736EEdj8ht\nuw+rZr4n0QB6U4Z5OlSb1FJHueKQwNYU7VHbOVXYZw9SkGpzu56rTJ4OcQil\nPmBjIw/3XkXqV8nwAUtcJh6YGlNhg6o0zBky6A/dnkwxhn6iHbgkNosBjfyo\nmjyU0DPgYPXStkSi5dec4ddOxjw0ZAz3Nluvbu2oEg4QF7Mi3Ai2DSf3VWoV\nsUF+MO2l/Q0iD7DX3y5lCZZYNIKvY23/phCGNfpdSRaAtYlHRsNZCvewDkxz\nVlol\r\n=86fw\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"61b0d187c5c030042fb90bb59c1ebcd090186cb1","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.784fa7903.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.784fa7903.0_1578510594514_0.038703092318730814","host":"s3://npm-registry-packages"}},"5.0.0-canary.823c050ba.0":{"name":"@material/auto-init","version":"5.0.0-canary.823c050ba.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.823c050ba.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"3afe83fa61f0853d347d7ee37c9979b1ecbca6a3","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.823c050ba.0.tgz","fileCount":14,"integrity":"sha512-YdIvqFqtzzdRBn+icXTP208ol7Ot+N7QEvbPUiklNma3ILvphputxPKCXGFPS985ZzeS+vWzkiVSXzNHPAMspg==","signatures":[{"sig":"MEUCIQC//0Ka9ctHgW7ksoaB8gqB2MMGOcBMgvgZIgqYn2q9ugIgSSkTaKROs64PvLcm/coq1Ga6cNK8azwNtXdahsn5mks=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFjctCRA9TVsSAnZWagAAiJQP/0YyiWlJ/fe6QL+86nui\n0XtP+H6iDruRBCxfrbUyTN1tTTYwQqwDcuNiofCfsPKpNaXV6eEbgtz7s0MX\nHA47lwaL+m2Dh3ePQfYDvBTOHNSlZEfqWifBFmiXbmsnYV+5MPMRDCAaYkJP\nCL4EspdjgaQE42qywTfAFKZi+YSel7sXnlnArTgsOUP3OiYnq9LlFlOADYji\n5+Y+dm99o5llfdL5OKb76ecRRU2CoqQDneV7tHt131C30O961Atugb8s/b8v\n/pLS04DBUEr+jsJ4/U01+NBwDBUAzhzL22nWvr7kD0sIv5s4O+T2wJ9fKNXH\nP5NK7vWAPwcAnnKzGutuk0RX+2W+78ye8PQXs8TCBTU2Nr4UFYymeq437zKm\ngi5bkEQmGASesTIP+CrWbQeQEiYu4K5j4Guc89pgSfNwFnaqUyyfCP7EUWVT\nf/yHQFErMzMFOKTrXGH6bHjzV1MhfM+LKqwrGpoP8YBGkBn2gpviDOTQf1Dd\nbm6IMDnPVj3bhmPj0IJxNxkeWRASAwpo4H+JldTrYapoRuZUvHfjmXwlUsm9\nwO+Ery+GgvYP5j48AXX5FyxFqzDk+EwmE72fRfay56esQsX1R/eHSGvlOo0I\nc23JYHxTD4jitZmG9EieWYX8cWYmXBDD6m+8T7RX3s3fjT2R7u8USUlWG+Jm\nvymE\r\n=Kx3t\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"b08bf7fb482cc6c0e80d365ea2bf510d80680bdc","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.823c050ba.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.823c050ba.0_1578514221103_0.8153100579464818","host":"s3://npm-registry-packages"}},"5.0.0-canary.70c708dee.0":{"name":"@material/auto-init","version":"5.0.0-canary.70c708dee.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.70c708dee.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"2c317c3fdffcfe6538a5bcdb8c63f7e2e90ff65d","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.70c708dee.0.tgz","fileCount":14,"integrity":"sha512-bZfTHtCCYCEUVN2jv76pwb6N8vfpay/Va4XyZIvQMz4Oreyc7BHYjxcmrdg9N/1zwf72AY01H6l/bwAHVtSw3g==","signatures":[{"sig":"MEUCIAO8+v7Oqi0xojMblHwmJ8SfwZOxzAKtR/NT2e/yJY8zAiEAmi1D3vxVRw3Jm9xq37qlO4D+S9NUS9VLo/2LXNaLK9Y=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFjnOCRA9TVsSAnZWagAA47oP/iJcFxqVaT/+mXt2faFQ\n+03ejwb+Yvn28oFM452fVl7RvIWofmde/4lkz5AMQBweYW1ShR5hg3Z63NFe\nz+WgLUUX7wmCwJoXHIl2UGrlXcspg00jLaXbAYYTgkRIVWyNVM5SVgWDzECY\nbZVDX8J+0T3KGDyvMeCBw1SDtEStIGJTG3IOtoOGWDzPWv4NF4a/27ciejyy\nyL+mKNLH8Bm9yZlPWcX10O/70x6mk+UF4E6RENnKgxyJejl+S5YTf9Kut4uD\nVGZzIUvSWd5ERIjHVjfte3e2ACVHWyNhc4SLpQTVQtQkj+G17+nZG1Xbp8Sz\nR+Fi8dtySsVMNmey0dJLXh9pMuqVNRL43+AIn7T3S3sLFPC79Y7ks5RQ3buS\n/4C5K20y8d1S3G/2eAbHTQZ/3IJAZYohgmFvfqQ8v8P1JSIXBp1QgvVCiQxv\nDY+oltQt8kkP0olePMBx2BPrQuHRc3rhX0cDkzCMsosCAV3AzS6RfAM3YnRr\nnEGVnKE3+HnJZXCKFH8xDLqEfEip9QBWEyNSKzptmqRajk7jX+SwY9nGsXeb\nf+HYTn//2Pxm5oQ8vmGxQpoDUB0hF5H1bHxgtDOazMWktVt5aoGXJVrhb00Y\ndlGeJ93uR1wmC3mtfEIqrIWj3nAg6FnqzhA/2HbcciSVhtmayS+jHbHpAW8g\n89eO\r\n=lWvR\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"096bee7c4a6fa97b650100f3d0e0cb484db375d2","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.70c708dee.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.70c708dee.0_1578514894520_0.598280903574373","host":"s3://npm-registry-packages"}},"5.0.0-canary.5ed9d13d0.0":{"name":"@material/auto-init","version":"5.0.0-canary.5ed9d13d0.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.5ed9d13d0.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"66847702fac9880211e3ee8b664cc18032ffadc8","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.5ed9d13d0.0.tgz","fileCount":14,"integrity":"sha512-0Eh4HSl7BJLSuE32vvSkBY0R/gduTdNY76eX5o5uXb3qmZUoLdjsPtkw3HV6e/KlS/3pbJ4ris66Rtb5FPsEbQ==","signatures":[{"sig":"MEUCIBuFhmMzXBaraLkJwdD3lCvT6+Uou9u6xEhvL1yXe8k8AiEA9KKPrtoWupZRq1mO5g7Zy4sLopnLN1aYiEjtO1W6UCU=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFky2CRA9TVsSAnZWagAAJ68P/3i0m0ssk9CJ+XZ9yowv\nLHqM17iQSH3lSORd6/aIqGrn8WFCxKMC8gophAaZbYYZ42rRyq29NbruhI0W\nHQFVzI0eLbJO2rc7xarLHTCWVmzs+GerLQoEaiNj/oY8LcBazes/7BpicpmK\nnQgR4RioCxB5ykDMi8oXybasJ+DTQgKZ/jVQP7W8clwRx2g/5WdqKSzQCaG0\nen0lAWgafw21qjfOGp1/TbiSReuc7wQy4bssFaYRab41RxZJDBAFwrIzJqgE\n9E2ADyvq69LN6RfDsaXtKlb22z5R987eeyytHgnY+bSenHgQZIp2yFPRoQ0S\nYv2r1jAB1vrGytmsjAF33UDpT/yPe6Sypyut2N4MjJCf+K6sLUOqolifZFE8\n1v0jJ+FdY4BxlAG9pqAHmjaYptszT1WkA3R6L4MnR3u4RkGFGOBeTVnW/2TL\nBHN46Zxr6IrJQlnxHQiZZ8eu9N14YaOZvA9RoaRdNHGsse25oVKTizwtgvQd\n5r4LFQOU6F/ogIAFQGf8qdve68b5ccWSYK4f3y+LeIhiPlTq4jbtSZTiA2IW\ne8kTtsQPdcUM/18U19cnaQZyEUhry75/nkNEq2W0qikJ58cfpGi7DvrITcym\njcBnNYK60XHm7h1Kaf30HPrSlE8JmghUjtFNdHNp+NrIYnD+AvWlaK5XCrp6\nbYec\r\n=vd2A\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"3c9ae4313970bc3335cb0223b3e10f3fa3ee8ae3","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.5ed9d13d0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.5ed9d13d0.0_1578519734117_0.9180774060882213","host":"s3://npm-registry-packages"}},"5.0.0-canary.4819cc7e5.0":{"name":"@material/auto-init","version":"5.0.0-canary.4819cc7e5.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.4819cc7e5.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"d39aa06023f0633ab750bc71a38bbf36cae10efd","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.4819cc7e5.0.tgz","fileCount":14,"integrity":"sha512-QIEBcXIN0zbO0i6veptknrPCagV7+V/xnizmGakMg0cZDahlnnT30ErVJ4H4PWtUKZTBiHYAc80PkoO+Ej9w1w==","signatures":[{"sig":"MEMCIGLckXy4AiTncpmE2tZ2dCxzhadTcpl+aSkg8PYa5l8RAh8nJtOS/VWk+YmPkypbvOsl+rK/dOaZnTEv7MMof5wP","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFlBbCRA9TVsSAnZWagAAL1gP/2axXZ0IM0c0SZcxUmdp\nstZu0u+l99g8uMjQj2bFkF7w0DzsV7/x1zG1DXb11s/bUZO5yhiCRk2lN+yS\nctobd9xOPyN1ft75U4EoK12w8WOP33MzJZmhyOnkMHV7LR1fpT01AyqyfBzE\nBd8W5UhKXZEk1bd/zu+cJNfZFzCWyReibb+O7qTdNG2dvcnXXWJlxLydrRiF\nFV0L5aY6r61PjCqsmGF+KkIOPiM6pEMwv8S5vfSH1K2ZYGRDJdpwTWhmzAqT\nTyAPSB0DYSMB3sEAvBUF5MOA/c+4MoO5xTlxCMJTxJhyviigjQLHWhXwLhNZ\n9nF3dAkjIrKCEoBrSghE/qZJKwSP/KzgK1xsvDEiDMc+b0Dz4YVqX6PUC15n\ncj87EWCJe+7gc8YJr94Va34LyskL/dFDaqA/PDYeizIe+47o+I6FHcLceZzm\nWb7jKFiShlGXGqL0PdjxMjGBVIO4xfSU6wkdxZynq/k/YxBOCAXkknUp19Ik\nMGu8u7DquSn7HVd7eBUedXmhPRi/KNomMPbCZoivj5uSvzkUhPksQmwrpvYt\noLcfAOvrz4VPoOqtaImYsjZA1E8U9j+N6qhgW15lN0MuuKhYI6o8pmxJ1r/y\nbZpA3M0XJzdtjjGk3ISScPn7Z0rZUdmz8dOCIOpztxxAy6BF9ZTI5frINVgS\ngXVz\r\n=QoZe\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"1cdb8bd7292ce5180cfeb2b5ea0cf8eb4aa6a931","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.4819cc7e5.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.4819cc7e5.0_1578520667214_0.2021378730677037","host":"s3://npm-registry-packages"}},"5.0.0-canary.fe3ffd2c3.0":{"name":"@material/auto-init","version":"5.0.0-canary.fe3ffd2c3.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.fe3ffd2c3.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"81664ba3e4b10bd06573f6f66a02dff32d43e754","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.fe3ffd2c3.0.tgz","fileCount":14,"integrity":"sha512-JdalAgj3YHIm2m4iAgOCYABSqJ7MfVhLOBhO7ytV5BI6pWYlWwSV9MqqofBrZG1BxLUTl5Idg9g96laZKdq0vA==","signatures":[{"sig":"MEQCIH2TYYrXhwrVZzEUfxSR5YcsAVqagu9pieYnbTHrmV9lAiBtlRv5Nt4DdSA20c1OXx/BNsLOMCS2oSIZkJqA59zDRA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFlSUCRA9TVsSAnZWagAA0iAQAJXRVBMCkawcyVtpTNjo\nR2IqbzgAI3DVNbuNpJdyAgDsfi2n9QcURFZXdGqrtHaLH7fjh3Uy1Hgr53nm\ntobbNX3xse3BZAbsKJMbC+zLBw/TVi+rKvKyf/Qb+A2FYI03nLFmYmMVMR8f\nSMVp4ta8YjHVhYZmkl6aDSsEaLVFm+gt/N74px8wqbQnZLON71gVNXVoF1Jf\nFM86BTB85mf23kBZc7E0F2WbbbblO3h6yqvC2IfyLvrYGIRhSEmKsbqxxEKE\nMageoOtQFJSV2PpaNkE/vPV4fV2CMiURMQuL709ce/LhX7iwDSA61/N4TeZv\no0DihHcBHaoh+MI8LaqOSmEhuduv2/Ag8JwDzkGeX2bYEjMd8rDjBih0bMoB\n6NHmTpRhNnryY6WHfKtu/TQ99R1s8cg04Jnbq1TS5UrObgg9Jv8W2vXmrm9H\nekcKNe8xzbOQeLCkc1fl4Ck61JxeqTm1aV/93xT1W5UeJnBoV5Y5Hoz+PByZ\ntBf22sJaAM09Vpst8lyz4WQupSQ+o1OoL1PmAYY6fn/K2yuXQIQ4MRHyIxtb\nfFUD3DO7GnyWIGXhNyN9eSBVrTdW4Oc50l8uf6zQ+wJJIblUku16f1UY6TBN\nhNbij68s2GIjRk0PSd14d/KUCPuAOzctk4sxi2+C4dnr2gvjt32xRrAN+BXh\nvrY1\r\n=yoNW\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"ef82dd049d6c2d6439fc79408aab4567780d26f3","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.fe3ffd2c3.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.fe3ffd2c3.0_1578521748207_0.3610841407123351","host":"s3://npm-registry-packages"}},"5.0.0-canary.c0e850090.0":{"name":"@material/auto-init","version":"5.0.0-canary.c0e850090.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.c0e850090.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"4559f70c8dfecf7537aa15067f2eddf7d22a8fb1","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.c0e850090.0.tgz","fileCount":14,"integrity":"sha512-/hGms+Ai7YSbWOCQaep+STTPogKH6m6zUQ008IWmFZcmdKo9YIl7eZXesRssxwJLJPE/LLoc+5s1Az5KcUfxMg==","signatures":[{"sig":"MEYCIQDUj3+pO+fZhUdcWXQzAlt5udOamepHTHStx2WHgcf4RwIhAIIRN5wuDDQmUUZ6J3rUIerRj2v+mqX5yIqB48AyUxrA","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFlY6CRA9TVsSAnZWagAAlvwP/jav9ZRcNxzWkZe9/w0F\nyxWbYNr5zR5LB9T3TtBEAJAKeh5ElfrREyN8PwZXzW7CRtt6mTcJZZ3rmT3J\nDcI+jAMyggBFFw4/vXLdoBZV5xqseC/GHrHjSGEYY84lSkpjLQSVa/FvhRx0\n6hho1jBQaE8xl+1zstMHpnDRctPKORezMryV+wwa2FP+kc8NsWYODZD2f95L\naPY+rAmBtBfNnYyL8MOeeIY5PmN5xb7498Dz8zWZBHwGqS/Fz09u9q8PKMp8\nOd2z1Cxw6p+PQxSSHy1crTGY6RQlUroxeUbBVlNVTm+RMgErGdE9tEcTMTUF\n5SBjL3pFrrOidBhwP2q8lYxWjN2jJuwEtPQpFEUi+O9z+TEW75gaPmWSXk4S\nX20OG2oB5TBKrtKtrE4R2cy9h5Z7JYgfS/861eX+SNNPtQYhclgBBjc/ud7l\nOLILJfvvH2/+XNCv42qtf/uZ4lKU6ghuM6wZOiiRYsFdSnWuVfuBykCC9zoQ\nrqfjVjKy81ReDlq+VKaRu/y/CS5E+T2fanCXrs9GSLwvFRB+4hImJlzrm/AF\n0E0V6ihu259e7+QhaHyKd1ZL8rKv30TMkRkIGWTOGtmmPu4IRM/+tdiDaf+A\nm25ZDufizf1t4eG2YMp2DCoDjIrrSqO5MiItZYXiRAvQ/w9Wv5xipzqqaVTF\nWhD2\r\n=q1CV\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"04d9e991ccc9d40d53d67d592c9532cb43e763a5","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.c0e850090.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.c0e850090.0_1578522170078_0.13651413750089092","host":"s3://npm-registry-packages"}},"5.0.0-canary.615f86f38.0":{"name":"@material/auto-init","version":"5.0.0-canary.615f86f38.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.615f86f38.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"1383b45c8bd29f6c56e0acae4a3cfcb1cefdd550","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.615f86f38.0.tgz","fileCount":14,"integrity":"sha512-tAl4FwZam6YpFx4g9Y3XPFAU0awrBf67YXpD3wTgj5HphhUyOaLRQSBq5hHY6n+w4M7xtK4IdkOK46CqRwMzKQ==","signatures":[{"sig":"MEUCIQDBMJiPau4IBEACIBcdC/Ey6EOZUzkMq1dr8DEjK+ko+QIgFPVe8q4lLnzhDGRYVDiJAX1DkO0DJ/xAbEuxsVnOyvs=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFlonCRA9TVsSAnZWagAADScP/j3gEdEFyNFZdX+kMkru\nVdooUPb+ZMIv3uABM0wmh55/TaOh2weByjqM9uFS4NPobBEMYfFgrQwzpfKJ\nVve/4Vzi6v096gP8mFAX268grS8baKZ1bIynbfkKcCJs06ci0OofdnVbsB4y\nm+TAKuc+3XTN965irFPjkaSUQE0l9b7GEwNyNlfq/iiMgqyMMvxIYpUW8bij\nZ02tPrCGFgghGxQX1g/Ul7FtNV3fGx1ACAeOib1RJ19T7ZhZ5/Y8w8Ow+ucf\n20icx4+DA1/iWBiobLxVkMnr8qCM2n9SBtSiRY0PYxGwSsk1Z3EEu0OEP8f+\nS1xijBTLoGHX1CvRSsuRFjaEsafwtDG7LUk2nIgLbOIcrewKRDwqCwpqcRGl\n49gsycM/ROQ/suCoyrz2D2N2VVN9X4q7Dgu+fCPNJpCKOUa+nPGR0v77/UQL\nxzHW/PsCCB2rMVlDTrXREkDTD++jVuXoW17PoMwsRXglDn1S11SOuCi58x+V\nP9PkQb6LcI8JL7cFQ8K67FIQyu18QpA66qWUmaONPY7ILei467pTd0oxetnZ\nFg1MxU8etHYGN1omFaipvTWksR/i6M0Y/rwAj4+Cv8uMy4gzV1VzdbtCW7Vz\nLskft8lO3K/mrbZzMX5P289IACinqW/DxKOZYXRHZOSjq1cY4rPcFLaEK+oo\nyJom\r\n=EXaC\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"5ae8bb946c188918a80b70e03e7d35b1e27089e3","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.615f86f38.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.615f86f38.0_1578523175493_0.20313832897253037","host":"s3://npm-registry-packages"}},"5.0.0-canary.1eb032637.0":{"name":"@material/auto-init","version":"5.0.0-canary.1eb032637.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.1eb032637.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"64f6efb2d8910e9bdc5f27df3619d462fe45365c","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.1eb032637.0.tgz","fileCount":14,"integrity":"sha512-LBRdjFtIlH5uXKwxGZYFLavOGJLtojJx0f5ThaOQJyAlJyEWtmtQIz5f5gQFZKKJaSh9HgyDkYqUgXH0veEVhQ==","signatures":[{"sig":"MEYCIQCf4RTD1rLIIjitfw7kxMa2hpQ7eyaONovKO1AhjWjI2wIhAMtuGUyfHWl2qgwId38Nlax/U2lN19U7MmmRijPWeQA6","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFl7XCRA9TVsSAnZWagAAbWwP/2n7rzRa7RV67i3wMzUR\nWMlMUuptZ7as+wD/fCpOT4q5xcS/UwXPtb8Mo0hHT2H/XxliZi/qHniOqmkb\nX6rDoZv3DT8lvkbbmRwUpaX151VT/VCS7vgmzqS0e/0u1CZR0ZmcudFsq0hH\nCebLpuKUB6A73cY/Kk7TIQr7G4Wz3aX9t1HmA8SqpuOg5SGXEvjy9zXB9GHy\nhGEhhHHwZs0Rrao6p0uTtWKdeZSNgtR8bs9tT0jTudea1zqCnJslCAKFaAzO\nE1Hv6nB5yFyfx99jV6FBVljlohuZimCLDOwHxDHgr210Fw59l/wS0o0V+SdJ\n0Bn9VAdYAi+eRxty0u23rV0MzJpM5+xtW6S7F+c9uGCakUIbrQeDZK3rTHTS\nBwLYyPjeON8UZYwzt15CVxpZI3g5bjCrfBHlAxv3/s3oHy/uHRBGoaoFNxyV\nxBk2kuan9XGd7KtXIcsBXWKik99/P252h0DZszBUcjs4sbVgIyw3x6BlN2M3\n4hh2Gm3ApR8cudBL36XruRz5n9zvf6uM7MBnyVLSBcLzjFYBZHondvoxUU3v\nZz4ER8Y1wr9H/Ccp4gyTMPB1eIiCIZwW0WP4Q1Vp4UBu58nTKQAZR0KfiLFp\nqEFE458S/ZK3mO4rGDRnbiJ30okd/TZoSLZLCIfvjHesSMCFze8zZc5C6ZVg\nyo2b\r\n=A6S8\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"ebd5efe5771491e06a78d3b1ca6b1af49af8e943","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.1eb032637.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.1eb032637.0_1578524373785_0.034260174278474276","host":"s3://npm-registry-packages"}},"5.0.0-canary.5bc5ebfea.0":{"name":"@material/auto-init","version":"5.0.0-canary.5bc5ebfea.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.5bc5ebfea.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"c6c2f4440c7f081289f84e6a6a656a0c464ddcfe","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.5bc5ebfea.0.tgz","fileCount":14,"integrity":"sha512-76VzAs3f003XIMzEU3GrFShs42uNguxvYOi3kNXxDPNTQ85913v+wylg1pGSOOUaT2owp4xOBVxC5kScaFRAbg==","signatures":[{"sig":"MEUCIQCh8b/D7JUnWAw2oJqWO+i/Ruv+MDoo+mJ18BO69aHWOAIgX8IcQJbUKSgixWzE/AcYSXEbhXCBHWHcGV+Rqz+JM3Q=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeFl8HCRA9TVsSAnZWagAAzJEP/3wttp3OTVw/pZj890ki\nbowfIMdb603vTXg3YEO7k7nMREVr+H1MoJceMyKoeHw4bDbEgZ6yevATYNh+\n0ClnxiDqtEMzJSQiOO/Kv9ALa8DthHxHwfkoDQe7FWATVS3rxnwrJG47KrTH\nFH3wYx9uDbeSGJFKt/z4xvWzrwg9ofqtcOOxc1W5ij/37IoIy6XRMVA2/thI\nB6Im/X+WTTZdFsTM5ihUb8pE4qjnrF/tfU/QUALc/f/eOxATjQg5jkyDSLQU\ne3jM6xBvN1pBMaUN+Dx/yPmJ07JOjJ6vaSu94Tb8ids2XQoFS4Modvcszby/\nrgyG/Hg/Jhff77fQL4sErgua1FC+xXicxuCJCVcxlfhRiaaIMxsTxkEv7X+O\ntkW9a4s1KJWsiq+q0zojbbAkIkPzm1svOTxz4RpQhs1PXihwEzFDW+j4Y1Dy\nxs5W0QLElnaD68lAfUcbgRTX1Y2MK4Lf4N8mNPAPmhwrXGPEorEihyFmsvEH\nbASpOSu3BxGxJJsCph4VoB/c5ntjg7PCYPUsTZuwyx9Rb1Mmo8nBsHtz3kBV\n0Yt7rrCyli4t2MLxr6zAzWLjmjEtkjvYuvWBQQWBofp1QQ96twQJfIJOomIJ\n63FRnsLYM34Scys3uvMhzf2WS7tYnSIphe9exe7D8+eS9sITRumylV8MQwQ+\nehAX\r\n=3oRX\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"8d87a9536a0b9e4af0865ecc4d9b558a6c193f33","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.0+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.0","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.5bc5ebfea.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.5bc5ebfea.0_1578524423130_0.051351423059780466","host":"s3://npm-registry-packages"}},"5.0.0-canary.1112b8def.0":{"name":"@material/auto-init","version":"5.0.0-canary.1112b8def.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.1112b8def.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"86443e9636cd51950a3dcc57570c69ee4580330e","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.1112b8def.0.tgz","fileCount":14,"integrity":"sha512-0L2enSMa+/Le7KAsqY8vvzZ6dxIGAzhgTx1z7OWR9g4HC5EBmlRmrwbjCMAmHKQut548PrLzCHGOSBwYLLpt2w==","signatures":[{"sig":"MEQCIGlUu9eEaxkSMorab4/VHyqASZNnMXxw0Nq6fAiqQ5q8AiBX3To54rOu26tho/Le5WyAChAiiPs7NqHSFo7YoJt1yw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeF6SlCRA9TVsSAnZWagAAqUoQAIjhyCb/SuSfYNPxTFy0\ngJPlnTWONwfmydkfdw/5O4VwtjfEuBGYglW15DZ0GVur8zbd79SIi+B92ahG\nA6q6UgaLq10wulIXcaOcwOzodWSFSauCndTDb/5ZboPPHN6cvzweyyGOueUM\nLJhIsa3ieHfVpEgeEPU4EGnPOMJQMHHacfTB9Pov0/g9OAsP5hbtFgWz2AIQ\nGTK8BVNCDSfszU7AyujoqboMf2HfdwH0DPfYcOOvuLB5GYj7u2pM28ftN251\nwTIcBCmD2D788++5OnJWz7U3TrkixtbywXthhD4e1VZ1S7Ur0kH0N09Etyc1\nMfRzILzZ/MyQzcZ+HXq3ekSWXNHFaK48L1VdP17UYmld/7C1AXB5rz59Hfc0\n5Xk1glnwb0yFxt64IVUOnaFi5m8QgHFGHA/9PXBKJ7E7rqXUdMBFbe8+QUbH\nWUuV0XBv6xRoiVGu0mer4mUH5b/+5IqHeL3Ll+bF+CD/iYtMAFYMoDGZj87C\nAEZbG00vsaO2NVbQHV7nAS1gdrxR4sMuqQ9OgHLvpTusQzwPWYzDeAxa1GRJ\nMkAkcD5xQwR2+/HRdhFHYl1gmeVPfjr5DOLO9DDkErlyH5N2wCbV1z8/Prmz\nZet/iGGC33Gp0YGmW3+AqznQGZ4hfFte+OfN5qzLL4+L+ZxU4yiBxh9kBYDB\nVPkS\r\n=4VKe\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"3fdcad176780c1976528d217d2fb149875bb4b03","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.1112b8def.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.1112b8def.0_1578607781337_0.9753470771141812","host":"s3://npm-registry-packages"}},"5.0.0-canary.aab102017.0":{"name":"@material/auto-init","version":"5.0.0-canary.aab102017.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.aab102017.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"ba148a9b1b740c04d7de5da768239fcf539c71cd","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.aab102017.0.tgz","fileCount":14,"integrity":"sha512-NN03sxkt8mLCgqxq6bHdRitj+I77JCWrKAEHED5//IpHCZIZi5+DlzWfAbMN4sgaMVJlS+OHRXSCDA/R8o2Dkw==","signatures":[{"sig":"MEUCIQCi7jQRfo+O75+B4quGtJG7akIypcHL5C/4bKNsrOEOGgIgSkM5dYx2a6ncaB0V2anktOrnQAjVQfbKIm0UcdMu7Ts=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeF8FKCRA9TVsSAnZWagAALl4P+wYh6EdFvKN10Ao9BeW5\nmJhRzxNCIKbekdzNvIl3XzHEVAcF5+2hBHNHlDD7w/4jD4TRluZTwvdxAq9d\nj4jInGeTBhgS6hG1LlEBCiy+VA7uek+PYxHyAAXkUlmY4KtUq+Fxq+zUW728\nMPjaAxRp7hVY1IQ8pAFtfoQVjgfnK2jY28QMNLpfMmr+PNhnFhkpW/4LTwBM\nWOZxuA70EG04GZjcGMCEBqts5ZiTLOeoQNm1yLIwblzZxKjIKwUKrWqlNKkV\ncEVeCcZLH2HyhWRODhvKB7Y2JqZguN7rKp5QtbrVZZXQwhKnBBCmy09kCMiQ\nQekQQpd8r18CdWFXOrwRF3Q2afMtohYFPSRc/mFNXsqGNWkO4sapdARHy206\n0KwktIpI0FmWBj0STCp6ceqO7nd832B42VXpm5sdA9B5VrKCZp0OyCfdvTET\nrlj2QXHgkX6z48TNHniBmrW71xsC0fghUXGX5OJsnVZzkuV8Q1sfsOGS+dwN\nsSHy72UVl2LU4uiBbXMGZaa6yBF6DRRJ+kJX42quW5Kf060u0UTWhnueJQGp\nOVEYVn8Nq8ImDUqrz7dm0LlYu542Q+Ct+Utgpl85Nv3NC0ZzKI0dOI1ncfH/\nEwjIGWg3yYDg39x0fDvzqP7KF1FfE34LIqhVNvnPhVaQJJeyHagWRsvcTii0\n8eVJ\r\n=1Z4C\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"3f5eab02080f0c4fb48614a44647ed55d55eb9fb","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.aab102017.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.aab102017.0_1578615113564_0.4827943136843236","host":"s3://npm-registry-packages"}},"5.0.0-canary.426913342.0":{"name":"@material/auto-init","version":"5.0.0-canary.426913342.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.426913342.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"2c4e4c23cd25a8823b96e81bc99f55e2f68ca617","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.426913342.0.tgz","fileCount":14,"integrity":"sha512-laogpfmA2c4M1Re+GrEjJCRoLIYXB6wqY3Ip2lgy1DANibv827QVBjhgeAC8r5EqNEup6MqPqIcZiXVSBI8yDQ==","signatures":[{"sig":"MEUCIQDsCOQR/S6/98nkPHVGlI0e9jNN4ztb0IdtaFiK4CiXvwIgZPnQRRw9+VRk6c7QuPA9qWxIjN4GE6K+0xp5ohEmRNI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeF9bTCRA9TVsSAnZWagAAFz0P/Atom2/JEVmrZRTeac7n\nrIubVKelu+s8l6fOjweBNkk4eoqH04VZ4xc2FoUu2TISjGPo1dqjpkrj1oVZ\nO3I8ldqrMCriXNaIn2Pay2LrfMQKgY+7PgB38UaXhBBUne3pWw7kWaTec9+B\njLoBJS562/JqWZOcts1px+joRrAIl8L0spXmMnJ+Nkvn3Zbdl+TW0prCBoXa\nBItGIoS9vyLUPCQwcjb6DUeH0ZP0fOq1PzvcpgzYkEq8dXVH2R1NlcXc5zNr\nE3PL6wANKtjDKBPQXePJTYOGWa6T3IueYNle/zwwMw/fhEZKk8+PgBnS/IVO\nsmFuJymFvJsVSeEmcVMn98nvDyBo0PcJpoLm5oMJofhof5FFlX40WWKXszTh\nY64+taPlugXyRPvWKHc17cjnK/ASTfPq44FRaat3bGOJcDr/gQ/orF6MmKSS\nwujjByouf8GnRqpIVC8bTZdbMfM3m2oGJ1O1IXbpFNb+sar3x5Gh4yZWznoh\nW5MGAyKlM4n1zYgAXxBc1cUNN/BjHUn1VyUl2m9PkCefceOhbxjT+fBNTBCy\nPetC0r8v3cze28xvRaaWD+0KJUuktDFMh+WuOyHemBISQ9jO2rULg9YAxUaS\nJwCZtA5tRb8TRIqHd5x/O0TmvDY3XiIJbA8bTROFrJTnFhkU6TjFI1qpfRRv\ntCeF\r\n=/Ptp\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"7a6219dfe8ca1677971694ece39ab423ee8879b3","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.426913342.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.426913342.0_1578620626643_0.22639837154192421","host":"s3://npm-registry-packages"}},"5.0.0-canary.d4ea9a706.0":{"name":"@material/auto-init","version":"5.0.0-canary.d4ea9a706.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.d4ea9a706.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"15719b30a364abdaa1b1f3c5ea368e8fffe48054","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.d4ea9a706.0.tgz","fileCount":14,"integrity":"sha512-L1wLBlsTIsAQixe/7QwmyFn/yTcPplYjHyFtEtRcuXrHgMz+o296hhFBB7h0Ojz0e74AQyoGJRXEvqCyiFWIcA==","signatures":[{"sig":"MEYCIQCTyyKo1MCvgAt9b4o83MJIfLKII08qp3yuLGMBy4VklwIhAOlbzgvX1sivYUDKbZHhbQPPGhpkz1coVN4ufxZCvK4S","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeGLNkCRA9TVsSAnZWagAAUf4P/3ySPuKxUUyBiEXJ0vfA\nlltRdkZNDnbgojWVOgFG1zHx4bM2P2wTxSj0uVfLTk1BB8ehsKBVMv9uCGEf\n+nG/D7O8TVViGorqUmeCKiB4z/CJk+fI/DP8kP/P2pHoMnTVq+fDpyfiMl44\nHeRdZOstzSpSktO1oJCCYAZvo3RehbPviObxKafVnzTCs0T8lSGi4J48y/li\n2mUJV8KPY05lJTxDEGGXyCgnZ0ZY5LbuCAMtaSolgA+jhz6sk0+XyEgOv63t\nkfaHv4Ktaz0fH6QNwW4huIGNTZnG2dPz5J6BtuiJDb/wX4onR3LJQmG0YaRy\ncOrhnHXwrcpzq+6RkumtPMJ6xzgMBIQJPAMAzV3F+gybsF4jEmYPg/s78ti9\ni80aZZcp2TXS9DLAlT9KWCLAaGvLRWbazedjYfftOdo91cc3zSH2IS1TXypD\n4Dy6g4KMVu8QtzxcerWjdow3RmMM7Y1PaEoZ85XIsBNrdaWiHUoJ+rEGlXFd\nKvLjRxEGldXxAt2jLLDPQDD554WylnvZXYcudMfoGtkwOmCNQp/tqUQ+cZP/\nzyjcNrv28AS2F9M8CYg6vpm/mrLVH9E2w9556AnmgZ7lnR3DXfSjgjhqImj6\nB90QZAm5CbwyaYJ8y/iqc564rxerSW4mFVqFA/EDsQ8kvi1oa8uAgIHVNFYz\nA6nH\r\n=nHfo\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"f4f80c96af6c2e34c34a3ed8f01c1858ef738935","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.d4ea9a706.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.d4ea9a706.0_1578677091722_0.18161221810589212","host":"s3://npm-registry-packages"}},"5.0.0-canary.7d4ee2996.0":{"name":"@material/auto-init","version":"5.0.0-canary.7d4ee2996.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.7d4ee2996.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"01aaccb7b7cf5bbd120416acc5da40df65157b30","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.7d4ee2996.0.tgz","fileCount":14,"integrity":"sha512-P7EMLkoKbnZuhieigQy+kddFktqZjqkEuHqrhAqMULlhaxTZPIHe2qlWGBEHWMTy507a7MN1xhVqhq5vSe5ZRg==","signatures":[{"sig":"MEYCIQDvSHxkDIOSz+FwN9v50GHk1U94hvYFUV1Lz0zb768+pAIhAPQh0XWNX3qRR1OVc1/1/dTLmvSyuDFYLrk+h9oJ3Smn","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeGLrGCRA9TVsSAnZWagAAiYQP/1tAU/9MFw2k35DR5wFB\n2icH6mCeamsQa/8AezTrKF2w3hNbOKifnFhBoZlIF+PPeNEOlGDVXmSJFDck\nK1iv7xnIn4K9eH0JfGwUnr4wnksAo4o8+g699+9EhTKi20fKNCBDB6f0qB3M\nrl2tVgDhufN2Hbo+4Fx2tg0Kan466KmJ2BvRmPEFyvyQ1ucw8P9vey9bGrVH\n9X4H0qkuwAxUoUpDqtVM/qG0ggxDD5CuWBvvnRzCnLhBDTiVH3djMF8OOHPx\nR3LWzaIfwzbMe34ub9WFgYEtkwPcb80JYIFwXyuA+OrlP+MvOjb3AWAkKLT/\nUdJ32zWGMu0juh0dDvxD6B9hlLDWli1LTJ6weD1DpxMIWFEEz+OlAVss0qeN\nKteiNPhWcmc8hgDylRbEPnAoHNj1eQk6BvZbASdkvmY6vJUJ7/0FrlWfdw31\ndb7kCREBpEiuJw1FgIWOZ8+XbtiSLslaZ/c8yIRIOW4bFiE9gyi2gYoxMVBR\neW2YrU0KR1hMno+MxLAz3ZC6fLPv8Cer82vWq9v0rwOWw37AB/OoHeBnNifI\nJAEKk/WHEOXRNpmpN8yWNNDbB/7s+/mw2YQnpFJj0lGL4n0kMWM8gsbAoFrh\niS5KQ9BUmIJBrlCWd7onkc6uZOgx5xTqE1j54mjck3ZVrm1l5CrBQrpdIKpg\nmpyM\r\n=A7qP\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"32cff7b459a8aa1e335c6ccc84213cff0f6e66a9","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.7d4ee2996.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.7d4ee2996.0_1578678981910_0.9698353889036142","host":"s3://npm-registry-packages"}},"5.0.0-canary.981ec9b6f.0":{"name":"@material/auto-init","version":"5.0.0-canary.981ec9b6f.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.981ec9b6f.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"679f3678317b6346cda54c28bc26d6310c13d9dc","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.981ec9b6f.0.tgz","fileCount":14,"integrity":"sha512-bLOsR84o+oJZd3Lq+3665XchA4TpYFLtfDPnv6uA3/d4c+eg87DP8PnKGqtthySdsvsIBdXS7Giiz8kfs0MZeQ==","signatures":[{"sig":"MEUCICi6aIYXPFWU9L1b8wrkiHEakobeGIOqIvwju9s/NRcoAiEAo6rcLBGID63swoLf2TXw68TSx5ELIZHuqPo4pfGP2/c=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeGM/WCRA9TVsSAnZWagAAfAgQAIor1nkxUAQDFCcfwjgT\nURrfz6disJFtSmJOmWCtSKMmdUGUjksdxS3LWSzVb6SLSuoGIezaBF1kY7Xz\n7lqb7XROI+jUnwabD6sE5yJtuYgekAltXWpoAMvEI5c1W91dH9YskE8umVxh\nHUQtBPppug7nDPqhzNQc9ftykrjyiA75iPtPWoqI+mA0bk99P2pi4YjqSWku\ncnEhtCdu6fB4UAvTGwOGBgjjOPZC0PH3aowKkQbFzokIOBSkZ+feNS6TwLzE\np3+XunWPRb9FNpbcZB6ZtG2Eltl9rYaEY7UOBTSSdtQPiUjKHyZkKlYAovlG\nhbx1lNY376KXVt5Ql9NMrYtBqT5Dd6W6aA5qyxzdXcwR45N1iSqVDh0oyTwj\nqkpG18FmU3CqTVcegV2B8c8MJk4hQ3u9uW5sWNKkyJhJMzifEmSQh44Nn5H6\nroBC6TG4XNZ2N2RNtMjQDpNYDJH6UANwmuVGFRc5U4rAsEhbRk4nWtamkAtC\npaeGlpn35s8G4YGl1GL10PeWkw0vG+1uaXeBzeHldOXg0/NAHaEQ+/Se2mT9\nCcBoiYwkr3qeIoWjBle7jvkFuaY10w4dhPDk8v8Sujf7F479q9RxR6E4En/c\nTCPR29mVWF6j5QLMgOiUxn/PGob3HhOBVMdqcMe7j5y8rynfigBthoKCRaX5\nRKXP\r\n=+J78\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"e2e9ae33775d14566dd45608f66087b2761d454f","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.981ec9b6f.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.981ec9b6f.0_1578684374035_0.7206125287335172","host":"s3://npm-registry-packages"}},"5.0.0-canary.737da83fc.0":{"name":"@material/auto-init","version":"5.0.0-canary.737da83fc.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.737da83fc.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"2bca05d527497e92d650e1cff79d2f5c8205f929","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.737da83fc.0.tgz","fileCount":14,"integrity":"sha512-P9ReCdNYK+olwc5TuyElTY7MaAYVrQufuTu8kWzRVi4yXJz/wlHW9DJGmuWliHSdF/MVD1EfFMTKu8YyZBO9bQ==","signatures":[{"sig":"MEUCIDgvX7ASYo5sMsVBTnY+nGuEj3hg+UEG7eiaku/UBsnbAiEAv+2iV/mmovkpnGXVmqedOE6L6mz22VzRZstwT7BzGpQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeGOoeCRA9TVsSAnZWagAAIQ4P/0lI9Y6cyG2NSBybiTlI\n7zFt8yqevlJTrWLuME20ja+IU85AeN54YcGy4mIljhY/PK5D03PLnyve0c93\nwxjT9fgSO4nJ3bZ4cUPqk9z38FV2vuvR3hLhhg10kb6Tg7Ln4opi8E8DXsB/\nJzIj/94/P7PG8qrop9sLH7Mu8xpU8cYghUdgf2zL5OyPgiOU/QUz7kcxS/Hx\njRi8b4K9BvVDABDefrzSb/OmvH9ubrAKZLjbZeX9JqgyYPKDZiBdAK3IN7YM\nh3p54m0IlJay1gMTa0hOSIyq45LGKiUoccgyTTXF4XJfo/D8GElvbZ2M9d7H\nlYGUNPBTWiWoNe1rRLQyfVe+U0NpKvP8wlq1rGO+2TSHhkEBgIsSZjMxNUaX\nBCJ45ZpzOixk5DCE4VA0AEDcUlbkNt/F/IyrYMDhxkKRJmNsLLa8qctgQeZy\nr7ldxhAvxmkkYhEma7hzj95u+J+QYmgblYQz5M4vRbOJkTS2vK+NfmDIbGDw\n2nxG4iPysXKMdAClxCOQiSJJqwgWslAQSVjPwtoD8XdbfKRYXe9d4VLGd9Of\nhHcbgLliEiCc+2HxXzCIT8NV7ysGrlAYY6uKSPd3N/Ej5pETWs+AG1dy3nbZ\nI5yKfablRADuoXaR7yWD8cmC2wo5S220BEJNQo0ZkuZWDRVDwHdaeCzVkN9h\n0iwK\r\n=aZeM\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"3ea8f6e8d81e688483ab007855dce5cba3b72015","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.737da83fc.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.737da83fc.0_1578691102405_0.4330962754250629","host":"s3://npm-registry-packages"}},"5.0.0-canary.aca8e6c18.0":{"name":"@material/auto-init","version":"5.0.0-canary.aca8e6c18.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.aca8e6c18.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"5eac6fd0e227eaaeccb349c272a6c74c394ddacf","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.aca8e6c18.0.tgz","fileCount":14,"integrity":"sha512-hd34PASV7pwvrzZiEAs5qEDsSst4iWcJZbnJE2Oub3xEW4X/GMNzXIJan7rhevNGO3elrWLw/pVAORzaQu9dgA==","signatures":[{"sig":"MEQCIDaPfWYJws5ALB2VgyNmnybVWgg5T/HygmLzSzDCkUi/AiBjelxdC4IpHrE5jpere6/ODZhm5gnQmT9Wkxt9utuwrg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeHMV5CRA9TVsSAnZWagAAuYEP/jtXQTqAM4Ym1V6IY9sA\nWV3xevKMgfbIDkcS1qkhFXn7246R5lC7fTUOrkJNZKT3MhJhtLnAm57N1h2B\nbcojby9Bb4ogEBcEANuHdy3Yq2H7bPbtCiGy1TFLsMB28t19I0DRtr6zRtzS\nfrwmfQ2nC4lWQ7ElcKpXeFeLRfI02SC+zMRQgQPU1knLssx3PHJvjrIti+N7\nA72ap75flMpJDopl9/LxLcUg8gOSFQvNtQgtreSCJnH0PG+XVFqrlndU2LR/\nFvjprriSGdBy765EEHqv6q41OjWyS3hhg3LOk0zBZnFp+Ky0xsj32IVon6Nx\nTEgx6I6oD7DVM4B4JwbwvOstudGr/Ao67+EvTrKIwOtNQK6Hn+xIlmCvbpwp\n/KJgIIZ+s+JpZkXthkfkuv+dIBkfPPevg6NfjKy6rXVZGgpmdr7WuDrgKjyz\nOhtGji21wtImPMUVaLRxYal8W88Uv8ojdMzZKgVLBEzVH/xAbBGKrOItQ0pQ\n9+5t479QsmZmlOHn98qGXegPv8spyXrRw+yOKi7fFhDzhknhMO0M+uqFPcmU\nc9RU1PsKwRswHTMJZMGkVykhccZ56YH4fP5IGhk1W14njrkRsK6N6K/XnYvD\n1TEW3JesYcl6ZbmWRbq0s81Rv0Zsa/gQ6MgfAsDK1CMq4HE/vnhiJFJs/S7E\nNkxc\r\n=B5q3\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"47bc251033c39b1b8f816f8ae77c888c07b20fee","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.aca8e6c18.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.aca8e6c18.0_1578943865451_0.38546442760691413","host":"s3://npm-registry-packages"}},"5.0.0-canary.c38d84e21.0":{"name":"@material/auto-init","version":"5.0.0-canary.c38d84e21.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.c38d84e21.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"be064b6a0fb2575bc5633e0ce148fe1535fc57ed","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.c38d84e21.0.tgz","fileCount":14,"integrity":"sha512-X3l9o42QEwDVHrG9GfmYg7UHL1tr4onEFQ3peBORipg8IQeoIv+or5fQQNyzzBQ35bCN2BiO9iOc26sZxCx82w==","signatures":[{"sig":"MEUCIAj4YpqXgPrG4LgkWzT039WczpzVBpkBHpegqUBQxFM3AiEAu8z2tdAMU5zALEiCDOOkB+hFWIHWLcR5WMW8Rnj8Mkw=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeHOtvCRA9TVsSAnZWagAA1ocQAJzTpi0R+S+MsNeccBtN\nL6aySKOSrrDncRskyimX64gn+pEafweli2Oe3mUf3qLj7emd7w9Wc5Dxq4HA\nv3YHgzfMZYiHGq3O+4fpITS7ORm74M9HoBdYKpn0fzmkDwJquKHp30tkpIOF\n77BesD2CjUrvK7OcKXwf1o48BK4hwCPT5RjYquaJSDSQBjJV5XPyw+ns6gHC\nl35LwYXR+23aIJOWRb+yBYkjCQRC+zKxznLufO5QEivLiZ+v8xNWvXC20Bd+\neADZt09jfvnMcPtePqKlbMWDTs7VQXeU/6u/r0+Sw2vU9Y90CeilPbFKY1lZ\n8cS98qzZxUYjZbvUhP+k1UQYmc0EbWiexIoZzgO8tipeQwJ2SXReeXlV1sBi\nDuJpdjJXW+31EzrE3Xx/I4J1xQ1NZwlNn5C+CGvZDpRWc7TbwlqWLoeWn969\nWCYURTEFgPg2CnvEo+J2wNnje5cPU74VtynwQK2xXQpAP2hSZt3Q3sDAr3HN\n1kCeY0/2OllOpNSOEWIpqq+Fyfukcq8krw7CeJoqmgxQ1OWKJdnpaVzlmqSe\nRe9EzHFknps/hn52CPMoGamZqbzNxRiH+6cExdTvqd/wH4GNN9bTDVcOnpFp\nYJTTZgm550M3XN5LSOWeMqmXeLcqkm+5JW2J323lI7btdmCsb+EiYCAVsyrT\np24r\r\n=c77M\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"f283cfd55cbe9b1863cb96e98011fe4badbb1fd0","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.c38d84e21.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.c38d84e21.0_1578953582655_0.8092328405160985","host":"s3://npm-registry-packages"}},"5.0.0-canary.a4db5fbad.0":{"name":"@material/auto-init","version":"5.0.0-canary.a4db5fbad.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.a4db5fbad.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"2ea45399e3825345734c1318a1467df3e67768c1","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.a4db5fbad.0.tgz","fileCount":14,"integrity":"sha512-r5KlfbkbGaiJPhZBLAVrhwEuUMfRYhmNAc2AG6McrlRvhm+6pE+Spnmy0JIOo/Nq/pWOqKq+5+VIQvml3WCHpA==","signatures":[{"sig":"MEQCIEAjC8J0rV4/r1qoByYZYsBlT++KyB1EiF+EfeindLzhAiAau91a8f4iaKWjSLWuSKWqaMbMKie5Z9Y2POlyXCrKYA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeHSQkCRA9TVsSAnZWagAA6voQAIQX+XhIiBGtiGcJxmy3\ny4QtqPapEYiiIOIsytPnT2fUBnrjLIXaUatxz80AEzJ5I4C7dDxsBbpEiMLD\ntof0n1ZLd+luJBBXzH8ZyESqL8L7xaI+kbkKTwo+tim07z1mbs+n23l8KObU\nEQW8I3TposYtr/sk4Xr8egkHMZoTMp9z0aEC3zyyB2esXSSVCUCb24nM96jg\nCt3czrFP191s0draf9RlF4gsJIXJoGQb/rzp86RSZvjhBzk9HvKv4YsRwvnV\nJPzGssj+/8gbr1/To5tLhuYu8CWNIKT0f7e0TrjthKsCTu7Hm09zcfMhAhuo\n+/yNWYYN/rrmmaCwKyLMonD0sBFQy3dX9/MON9VwgJZ+5PVaI0zMOtOYben8\nhe3a+cgHpev0qw54ZqHga+oiaiGTp3i3Ywdb3kqbgZscwfKirbXO1rSjpGOi\nkqKzIb3MxAV0+IS3vASiOwtB7gkJLM5lxvuFvXqd7KAn92+elq4Av6M15qYj\nqU3OgXrFHg/HDDZSO6T6DGtPoMyntoR32pWIAmb8p1e/znSNxTq5z1DgX82B\nF/kE+ifTGTAtvOMCpeGe1flMLdmG2nEEjXQML7ljsP9Z9mI2/g853spGKVs/\nxrbyJvtNL5rSbguwfzmhTjoZ5CuGpNAmdOxvlSdFMaHXGtljwwlnYHQvrZjA\nuNds\r\n=0HB0\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"bb5fe141944679686f178779345a5880a89943a9","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.a4db5fbad.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.a4db5fbad.0_1578968099676_0.09750098906104365","host":"s3://npm-registry-packages"}},"5.0.0-canary.faa9af310.0":{"name":"@material/auto-init","version":"5.0.0-canary.faa9af310.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.faa9af310.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"5de86327e41185bbda910eae2d650ddba32c4125","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.faa9af310.0.tgz","fileCount":14,"integrity":"sha512-oDeQo7KUOQbqDpbnaKhMV3TZMW7lc4G9bzLE47qa2cUqWXTV6bGhJQTBai2nGoS4FG8XR3l7AlLVISrdP7rF9w==","signatures":[{"sig":"MEUCIBBNzcW+4y555QVt4Hja7cDnvVWo6wmmThgSN3t4NlI2AiEA233e5aiZbbfy4WGXWTp/ZOeqYo/dNGJQ6z8M58UXT00=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeHfG/CRA9TVsSAnZWagAA/rEP/1MS34+QFsCNCR6Y7Qow\nPks8S1Jc+H2ggTiPc7NnoRqAmHvfDwUIBsAdQSyGA1AvwzHMq3QywEpbAfjj\naDOL6Foj/9LSLvk9466VQOHq8EleQpNQFS8DexXVIW30rvxmekoupmn3FfRy\nesO/4tttdIijdb6ci+QhRxwmmhEXEUQLlCop+bU5uRexgEswTknB1VwQ38oa\n9SEl3wwoIXEekVWirBdzLI97srp0MW9kc1Tk1gDlogYopqsAZZ5qgxQZjkHs\n9z/x/l00kwojj7zsiv4FRVOF8F1nw2H7MDzltttjd47dDk+pYv7ys7Z/pIRb\n4o8UpNt1WHAcf9Qm15LO8pr5snBh79Cf07yQnZApUjtvloueuEQkjeaKvlGT\n4EJxw24oCUIczWsin5zxqaa+hy/pCNzBgBoqsp3usL+tG+VNW8CrStDl75wg\n3xX7Oa/J+THlMi6PfwFUUjuEgNHMBOThhDGcNoHPVlCZeCpltvgZS5Rv8CIF\nYjRzdf81DaWGJOb4na96gAO3Kzf8iWpI0VnSCoJ+/aslPlZ9bCTBZ9ZlKf0T\n3ZK/PvAqOfq725Eiv4PPSCR2p2RCpkIOsfKeP1xTafW1SgagIgRZcJGNGozu\n8lofEwid5QvmptcR+zkE47yKNQyZ845coCrrYUUPaNSRN6vhylHArpCStILd\nVBHA\r\n=iMuN\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"ee374355df19027c59f24bdaa809bc18183453df","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.faa9af310.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.faa9af310.0_1579020735081_0.4835319468577699","host":"s3://npm-registry-packages"}},"5.0.0-canary.60354c577.0":{"name":"@material/auto-init","version":"5.0.0-canary.60354c577.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.60354c577.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"4f3935ba203b1c3d86d9e41b6853672fc1cc2330","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.60354c577.0.tgz","fileCount":14,"integrity":"sha512-uTyBj+/jmm2ovHvCY/3NkvR4TkKyGG+GlyC5jTTQJ5sCIytGrJPaBPK1psk8sNDAnabcQ5ndN10L0uvhdtIGOw==","signatures":[{"sig":"MEQCICIKytXWYZWZlbkdTiKaHD0U8WzioG8UVWrwJR3kAlt7AiBHjU++7jv87xWBDXLBA0zsGRtEvYIsATyQIv+uhmm+gA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeHkSMCRA9TVsSAnZWagAAksIP/2YCF/dY2mc+tzmRxLbt\nUHI+YuN6y4Xyl38/ycfJPyv/rZ87LYitR73S2eBPCDFgXO5q8sbwzqvVgvEb\no5U4F54TvLjcUDErPNGyu5SGkhTWcqe831pOqKUh2FiR+fX9dMaNnKYVeVMb\nnfJuQRVMb/OcfeboBIHZop71e/a9qxbcyultSkzBpSV4Kb4yu+PwDIl1Zeay\nJmNjdjMEAYypOIYPOB9LwyqWGiyNHUomL0OTqPnzyR10VL5Q7x2SNt7m5gvp\nXug0VHaPK05//kv3WTH+zvln52aGV3tmt6h+d0z2V5KAav1jv9rabuxKePho\nXm7RuB943hdJxbRu0K2nHNOF10r4ScqS4uwyNGB1/1nnfU5ZXnNWRkz49G5P\nxkgL3latSp2gkY90AKkdWcmAufG/YXphxiqyf5N4dJLFe3BOXqVU1Aa+jJls\nlWBMGqULz1EMTkAdmTfSLiLv/rbmW0juChcWS6TLEw3w72RwDUFvPom0OeYU\ngjJLRI5jOB2n4d1YH3HKcb45Pg1Sqwqu0g1OJmstLZqDeubEYq65hcQVE0VZ\n5H2dnF0t65WUfAzSSnRVf0Rc68cwevup8b8CLMcdn8ZpumdTKy82MJFr5m3x\nVNYClQt/ZYKLlrMY94e7o5sVMLjSxiIuDK+u9edQShDuUW1cROP1Xsm90W6n\nBRye\r\n=eNyF\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"d9f4420da446050561084fce698a543b0dc6b543","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.60354c577.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.60354c577.0_1579041932009_0.39522330214782064","host":"s3://npm-registry-packages"}},"5.0.0-canary.d07c78daa.0":{"name":"@material/auto-init","version":"5.0.0-canary.d07c78daa.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.d07c78daa.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"82a77d368db0faf6839df44d89973cab2caae255","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.d07c78daa.0.tgz","fileCount":14,"integrity":"sha512-S8CjIOeB6NFg7zeDrADVgdyhnQMrSRXwkkldHE46uu6XpfcTb8FvViL9ANYJypvBPCO+/5ImiJmFzzwfbTJ9Hw==","signatures":[{"sig":"MEQCID5oqFx3t/K89Vhoah6coHJ1MiBqwQ3UlMO0vKSPyHPYAiAmVFAK90f2WrUXgKVyrMKSIgccstQLmrI85m3kTVnSeg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50438,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeHlDhCRA9TVsSAnZWagAAgbcP/Rvs3tXN7OM/kaHT63DW\nZBWpMpmVMM/UhHuGGyc/EMNAGmUdCrp004QDnRpRdszkdCecU1qLPMHHHnVG\n3+uflRZItfv7nUQwFGjMXfDr3EOiQBNubDczmWO7Iiz5b3/A3HmbnuqVM8BW\nbA0/cy+AJl8ETa5CxoRRPCND/yWyp/CyUBeQaJkGAmTPAeygDrWIpf5KehsH\nOPpu4mO68MEXcmjKauvMm9s+dxYNK1I3/oZDkE/sx2jfVy/hNxqq/wqFUnhC\nD5ySiValRgwbGdPtlO8V9F5+rAGMsJPC+7GCLiQ7h2DAP7dYnG4wd6TuWSDv\n3MY/Gf8+0EHFIKWGlq5sZwDQlkomfhDGAPFgja748UCg7iGnFehuSLqnVPKW\nnfURqpBX+5zJ4/q2vww3KgJNaCyTAl07Hzx5iJopaWjF3Yob1GUGb1hhMitc\neObGMo5q1+BwoF4vphaXYAmw4wi/gPoxtm5BjdWFyUU8bUz9xFdzd7VfdeOc\nl/H0MTLGW24aeqoUXRh6x06DfQ0/LIfW5Lo/+65c7MpK0ixdylkD8EovVPSq\nQYjeFOo/thfnD6/i3CsEbyiySo3nE3Y6hMHHcJI/oR7cpJHI9PoniNb5u6Zd\njKl6vrlbzsiRHE/o53oysoU9kQK4Ie2cJotJRYSG7q9ylc3hyY7oPmlis3/S\nShr0\r\n=UOH8\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"3657a12b1a5b9b1742b2749f6991e06a32416314","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.d07c78daa.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.d07c78daa.0_1579045088511_0.0349593374063184","host":"s3://npm-registry-packages"}},"5.0.0-canary.8ddd5c6dc.0":{"name":"@material/auto-init","version":"5.0.0-canary.8ddd5c6dc.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.8ddd5c6dc.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"4eae956bf451307947b0c38444a1175edeb0c847","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.8ddd5c6dc.0.tgz","fileCount":14,"integrity":"sha512-9jjCYbgn9ofUPW5cj3wAI0zQ0SrrqvuifMPI34jEQjb1h+nfv8NYoURKTINSWAiamu0cFMpz30kqr6TjykCaxQ==","signatures":[{"sig":"MEUCIQDcISZSAGMUBfg8umVRvmnhBK3vOZWMnsBbvHXzdh3u8AIgB2sxv2RGt/JRmPV5F0b1EMGd0swCp9lF3bmf+/jXw+w=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50681,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeHm4QCRA9TVsSAnZWagAA1s4QAIAmIIpOMq4TWmswIEMg\n5kP8d53xlm29Od+g0HOxkTxvbZuNWhzuJ5fV2HpJ9cxMN+XkI8YuezGIBV6/\ntldQYqbgjoZMycw3woK6Eb0HNp2r/u42+I7NF87JbFu9jfQjecqHsSn2MyED\nXmMZv64WAqISF1axBFGKyswdGqeX4pTlOxs9WAcU+gM+ytRwVWWgZLWADre5\npQqiAeHqc6e9IzO2yrbRQcESd7p1v4egDWJSQ7mXFoxcJOoP+RFdWpB4rX/Y\n8CHB/56TWzeLaPfLKj6C4JYxKRxyv5pvMdCJy9H5hvPatqbtzk/BLik7qa0y\nEBoXqXzvVal5eB02HcYk8YiNmoBymZGv2xMcLBNyXpvd+Vf9+yJ06Rbx6MkQ\ntzo7jZJ/AZ7vfyzZi/TN7YOUHhJEuLqyCaBWv6RRvnKNbd5TZuG4HOkyvOz0\nl+8gMWtarIshzLoxiKKMYQjYli/Qx4sCJ1rLfv3X6LFK0f0bYX/DyfGN9Cmg\nN0vGfkds/PJphY2eARgzIwT1y+PWuEnN20qZrrp7kSrdRC2RLoHaNS0SUhjN\ncmmcOL7QKvcISHaClAxq5/yNko4aqP4ffb3yaovETTcIQ2s1y8wZBcjdZUMW\ndOFU1ZmMzaqk5LXDblRu3PCYa1uGCB0PiDG6NlkAgXWul9uoTEHRQnWFbdI6\nbxnc\r\n=eYuz\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"939fade350708e559f107b53d2ab9d27d6f84f1d","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.8ddd5c6dc.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.8ddd5c6dc.0_1579052559567_0.8624041293096703","host":"s3://npm-registry-packages"}},"5.0.0-canary.a9511d870.0":{"name":"@material/auto-init","version":"5.0.0-canary.a9511d870.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.a9511d870.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"42505838a9b68c66d2a0b1957191b45b92eff4dd","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.a9511d870.0.tgz","fileCount":14,"integrity":"sha512-sQtt0hnhO9E4oytVTZCHd7i+YKv8DZZRHdp6AbC/JVX5D6DNljXBcAQLfORefyvp4XkMYEx+bivDXLHuEjIOUA==","signatures":[{"sig":"MEQCICbF++1lj9YnVgBj4Us9qTSswiWucWO9EtaoxzE3061qAiBuUXL/juKsKUWTaQxIHGL2jwMDdcYqWxx8KlaPgIhvSg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50681,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeH2N9CRA9TVsSAnZWagAAVlAP/i1fNgdRV/PRLETdp4ot\nr9VqbutXmM/TedpX2MnX9pdn1H8CyCannlGFNpxnulrKCUR1jmekkXQr1io9\nDSC6H/TLUO5N7nYYZHjmj6GTCDDGZBJavLXDfQ1uflJqcobG79eggviyuXM1\n7KC38iisEK0qOg+SmukY/q/yhD1rYjf/tx9eIaGJlC4Z8OHFnrtoJosG+6pu\ndEZKoohmnvnCcN0kQo/ZKTbLsrDCb3wuql4XaCMzGMydMx9Xqa/dwh84HNju\n0aYJwtegIGECixHi8WUgp5dRjpc+QwXV73br+HVecmPNEVjxY/4ufyGMn0yY\nqbZ7u6p6uGy3+kPoUsyiBRWDa96w/vRXC2ieDyZJX0G2AkCiMtUQocXKsnHe\n11+ohzPn1mKoFkGDRYlwAewGnLI/E+lIKznsTLdloFQN01X1JbWZ9kvtUloC\ngBOJ7+IDLNYO7uwoUWZTmQDPGvW8xPSYZtb5hUi8TkRk/eXOErqXQ0iSCLts\nIJBECjbLRPFbYj+E6i+GilNTfAymRe9zIEkOda/1esHXfGpbr6LiXAHaNgRF\n0P+B3YwSMnqsgjrRwy0Q1IbAu8xwHDHnU5L/qywYnQCmOz9xwTsYz2V8NFuH\nwPygdKv5LLdOT9D1C+PV64dGrRjC7R3JZh7UksT0TWiQUFf2Yfy7xF8uBCUd\nQcbm\r\n=xr9g\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n```\n\nOnce `mdc.autoInit()` is called, you can access the component instance via an `MDCTextField`\nproperty on that element.\n\n```js\ndocument.querySelector('.mdc-text-field').MDCTextField.disabled = true;\n```\n\n#### Calling subsequent `mdc.autoInit()`\n\nIf you decide to add new components into the DOM after the initial `mdc.autoInit()`, you can make subsequent calls to `mdc.autoInit()`. This will not reinitialize existing components. This works since mdc-auto-init will add the `data-mdc-auto-init-state=\"initialized\"` attribute, which tracks if the component has already been initialized. After calling `mdc.autoInit()` your component will then look like:\n\n```html\n
\n ...\n
\n```\n\n### Using as a standalone module\n\n#### Registering Components\n\nIf you are using `mdc-auto-init` outside of `material-components-web`, you must manually provide a\nmapping between `data-mdc-auto-init` attribute values and the components which they map to. This can\nbe achieved via `mdcAutoInit.register`.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('MDCTextField', MDCTextField);\n```\n\n`mdcAutoInit.register()` tells `mdc-auto-init` that when it comes across an element with a\n`data-mdc-auto-init` attribute set to `\"MDCTextField\"`, it should initialize an `MDCTextField`\ninstance on that element. The `material-components-web` package does this for all components for\nconvenience.\n\nAlso note that a component can be mapped to any string, not necessarily the name of its constructor.\n\n```js\nimport mdcAutoInit from '@material/auto-init';\nimport {MDCTextField} from '@material/textfield';\n\nmdcAutoInit.register('My amazing text field!!!', MDCTextField);\n```\n\n```html\n
\n \n
\n\n```\n\n### De-registering components\n\nAny component can be deregistered by calling `mdcAutoInit.deregister` with the name used to register\nthe component.\n\n```js\nmdcAutoInit.deregister('MDCTextField');\n```\n\nThis will simply remove the name -> component mapping. It will _not_ affect any already-instantiated\ncomponents on the page.\n\nTo unregister all name -> component mappings, you can use `mdcAutoInit.deregisterAll()`.\n\n## How `mdc-auto-init` works\n\n`mdc-auto-init` maintains a registry object which maps string identifiers, or **names**, to\ncomponent constructors. When the default exported function - `mdcAutoInit()` - is called,\n`mdc-auto-init` queries the DOM for all elements with a `data-mdc-auto-init` attribute. For each\nelement returned, the following steps are taken:\n\n1. If the `data-mdc-auto-init` attribute does not have a value associated with it, throw an error\n2. If the value of `data-mdc-auto-init` cannot be found in the registry, throw an error\n3. If the element has an existing property whose name is the value of `data-mdc-auto-init`, it is\n assumed to have already been initialized. Therefore it is skipped, and a warning will be logged\n to the console (this behavior can be overridden).\n4. Let `Ctor` be the component constructor associated with the given name in the register\n5. Let `instance` be the result of calling `Ctor.attachTo()` and passing in the element as an\n argument.\n6. Create a non-writable, non-enumerable property on the node whose name is the value of\n `data-mdc-auto-init` and whose value is `instance`.\n\n### Initializing only a certain part of the page\n\nBy default, `mdc-auto-init` will query the entire document to figure out which components to\ninitialize. To override this behavior, you can pass in an optional `root` first argument specifying\nthe root node whose children will be queried for instantiation.\n\n```html\n
\n \n
\n\n```\n\nIn the above example, only elements within `
` will be queried.\n\n### Calling autoInit() multiple times\n\nBy default, `mdc-auto-init` only expects to be called once, at page-load time. However, there may be\ncertain scenarios where one may want to use `mdc-auto-init` and may still need to call it multiple\ntimes, such as on a Wordpress site that contains an infinitely-scrolling list of new blog post\nelements containing MDC Web components. `mdcAutoInit()` takes an optional second argument which is the\nfunction used to warn users when a component is initialized multiple times. By default, this is just\n`console.warn()`. However, to skip over already-initialized components without logging a\nwarning, you could simply pass in a nop.\n\n```html\n\n```\n\nThis will suppress any warnings about already initialized elements.\n\n### Events\n\n#### MDCAutoInit:End\nTriggered when initialization of all components is complete.\n\n`document.addEventListener(\"MDCAutoInit:End\", () => {...});`\n","gitHead":"69b4f620220b7e580f5273bb82be01e5990b894a","_npmUser":{"name":"abhiomkar","email":"abhiomkar@gmail.com"},"repository":{"url":"git+https://github.com/material-components/material-components-web.git","type":"git","directory":"packages/mdc-auto-init"},"_npmVersion":"lerna/3.14.1/node@v10.18.1+x64 (linux)","description":"Declarative, easy-to-use auto-initialization for Material Components for the web","directories":{},"sideEffects":false,"_nodeVersion":"10.18.1","dependencies":{"tslib":"^1.9.3","@material/base":"5.0.0-canary.a9511d870.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/auto-init_5.0.0-canary.a9511d870.0_1579115389280_0.13689020213242542","host":"s3://npm-registry-packages"}},"5.0.0-canary.5d4b82bac.0":{"name":"@material/auto-init","version":"5.0.0-canary.5d4b82bac.0","license":"MIT","_id":"@material/auto-init@5.0.0-canary.5d4b82bac.0","maintainers":[{"name":"abhiomkar","email":"abhiomkar@gmail.com"},{"name":"acdvorak","email":"acdvorak@gmail.com"},{"name":"allanchen","email":"allanchen@google.com"},{"name":"aomarks","email":"aomarks@google.com"},{"name":"aprigogin","email":"andrey.prigogin@gmail.com"},{"name":"asyncliz","email":"asyncliz@gmail.com"},{"name":"azakus","email":"dfreedm2@gmail.com"},{"name":"bicknellr","email":"bicknellr@gmail.com"},{"name":"bonniez","email":"bonniez@google.com"},{"name":"bwobrien","email":"obrien.test@gmail.com"},{"name":"candysonya","email":"wangchan518@gmail.com"},{"name":"emarquez","email":"emarquez@google.com"},{"name":"esgonzalez","email":"esgonzalez@google.com"},{"name":"kfranqueiro","email":"kenneth.franqueiro@gmail.com"},{"name":"lynnjepsen","email":"lynnjepsen@google.com"},{"name":"material-admin","email":"aprigogin+npm@google.com"},{"name":"moog16","email":"mattgoo@gmail.com"},{"name":"patrickrodee","email":"prodee@google.com"},{"name":"williamernest","email":"williamernest@google.com"}],"homepage":"https://github.com/material-components/material-components-web#readme","bugs":{"url":"https://github.com/material-components/material-components-web/issues"},"dist":{"shasum":"263a958cdaf671cffae0013ed209ea67313dece3","tarball":"https://registry.npmjs.org/@material/auto-init/-/auto-init-5.0.0-canary.5d4b82bac.0.tgz","fileCount":14,"integrity":"sha512-ca8y6iSRYd631XypchM2oUse61CymfTYTXi44DpPUqnS9SvYfvkYUccPJUC0pBpxeO6qOIKX5UNLp1DRjErfZg==","signatures":[{"sig":"MEUCIGmaIolo6CmLoEhD7VFo8a9DvMz2GcKioCr1jvRKSA3QAiEAzsV2ryoF7jDFQctaqEh06yMavhjJlKPNyCCPUzzh3D8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50681,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeH5Z1CRA9TVsSAnZWagAA+PgP/1ptrIptpnrFvoYw7tSs\n6SPkJnV2aGGGqBxC6wEIfaNfbAwrFzXS/4jdSwtE8e7nyYdPaloRR5CQwUSc\nsYXzPNE5CZWfeloATzN+cdA0S6CTerFjZJwCMQh5FvdpPwSJ+LHK5qFfG3jv\nU6sPswSMYJzWTgxxvAJSutYagGEJGsUuMUkDsFJl/hPhGrO+uIpIeX7mJ5cH\nu0Y7vYb1CYziJIUHSCUSHDHcyJ1rRiFkXhOf8fSPIrbVjCbqmBgOyxCSK0BC\npeyHLjiHN/PSyjjuLHn+qA04AbVSV8KztF09OSm8pZIe7mHgzVIVIkGRv5p9\nO9YFToP2pNULUiueeDZ+HEOH4y99PyLw2BYQ1N4WrCz3HA9Bsal9lKxM4/4S\nNmy/MvLuACBQ60zeFIL6Z7WTxfU0fjSSoPM8yY7NlFTk3FjBl3gGPfEQssPY\ntpRVMDnCY4UITudY1WeFlNYwcLIie/fCCqQ05C8zJNoiN+L+Rs7TUmc5HTtd\n3QjbJ2lp9kVt5qywNKxNnu5suMbJ1g6HXrxcaVPmmkAw8wMHYNrfKtL2B471\nleTL3Lm4TkR6+5PLe1cCBupj9sIJ7HYOWJ2Hi38SNbTfmJ1FfTnZct8JyCml\naJf5GK6ApVS28v/du1AbpfLxCaiJHXFlfMfS1EPogfvSd15HI1BAbVs2hrNt\nd0fK\r\n=N1wa\r\n-----END PGP SIGNATURE-----\r\n"},"main":"dist/mdc.autoInit.js","types":"dist/mdc.autoInit.d.ts","module":"index.js","readme":"\n\n# Auto Init\n\n`mdc-auto-init` is a utility package that provides declarative, DOM-based method of initialization\nfor MDC Web components on simple web sites. Note that for more advanced use-cases and complex sites,\nmanual instantiation of components will give you more flexibility. However, `mdc-auto-init` is great\nfor static websites, prototypes, and other use-cases where simplicity and convenience is most\nappropriate.\n\n## Installation\n\n```\nnpm install @material/auto-init\n```\n\n## Usage\n\n### Using as part of `material-components-web`\n\nIf you are using mdc-auto-init as part of the [material-components-web](../material-components-web)\npackage, simply write the necessary DOM needed for a component, and attach a `data-mdc-auto-init`\nattribute to the root element with its value set to the component's JavaScript class name (e.g.,\n`MDCTextField`). Then, after writing the markup, simply insert a script tag that calls\n`mdc.autoInit()`. Make sure you call `mdc.autoInit()` after all scripts are loaded so it works\nproperly.\n\n```html\n
\n\n\n\n```\n\nThis will attach an [MDCTextField](../mdc-textfield) instance to the root `
` element.\n\n#### Accessing the component instance\n\nWhen `mdc-auto-init` attaches a component to an element, it assign that instance to the element\nusing a property whose name is the value of `data-mdc-auto-init`. For example, given\n\n```html\n
\n