babel-plugin-universal-import - npm Package Compare versions

Comparing version 1.2.6 to 1.2.7

package.json

 {
   "name": "babel-plugin-universal-import",
-  "version": "1.2.6",
+  "version": "1.2.7",
   "description": "Babel plugin to transform import() into its Universal counterpart",
@@ -5,0 +5,0 @@ "main": "index.js",

README.md

@@ -147,4 +147,5 @@ <a href="https://gitter.im/Reactlandia/Lobby" target="_blank">
 ## Caveat
+- For chunks to be properly created--and since their names are automatically generated for you--you can't have different chunks with the same name, say `index`. So instead of ```import(`./index`)```, make your imports like this: ```import(`../ComponentFolderA`)``` and ```import(`../ComponentFolderB`)```. Notice you're going back one directory--this allows the chunk name to be generated uniquely even though the entry point file is `index.js` for both components. In addition, if in multiple places you import the same module, make sure they both start with the same base directory name. **Again, using `..` is your friend. Initial dots and slashes will be stripped from the resulting chunk name.**
 
-Lastly, to the discerning eye, you may be wondering if the return of `import()` is still *thenable*?? It is! However, if you don't call `.then` on it, somewhere (perhaps in the components like *react-universal-component* that you pass it to), then it won't perform the import. Since most of us are using modules, which we need to do something with in the `then` callback, that's not a problem. But if you happen to be importing a module that does its own setup, such as attaches something to the `window` object, well then you just need to call `.then()` to trigger it. That's a rare case these days, which is why we decided to go with the simplicity seen here. And yes, async await works too.
+- To the discerning eye, you may be wondering if the return of `import()` is still *thenable*?? It is! However, if you don't call `.then` on it, somewhere (perhaps in the components like *react-universal-component* that you pass it to), then it won't perform the import. Since most of us are using modules, which we need to do something with in the `then` callback, that's not a problem. But if you happen to be importing a module that does its own setup, such as attaches something to the `window` object, well then you just need to call `.then()` to trigger it. That's a rare case these days, which is why we decided to go with the simplicity seen here. And yes, async await works too.
 
@@ -151,0 +152,0 @@ ## Contributing

No alert changes

Improved metrics

Total package byte prevSize

385064

increased by0.18%

Number of lines in readme file

168

increased by0.6%

No dependency changes