@normed/bundle 2.1.1 → 3.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -75,6 +75,10 @@ If you want bundle to delete the contents of the output directory, you can tell
75
75
  yarn bundle --clean
76
76
  ```
77
77
 
78
+ ### watch mode (not yet implemented)
79
+
80
+ Watch mode is not yet implemented.
81
+
78
82
  ### Logging
79
83
 
80
84
  Increase logging with the `--verbose` and `--debug` flags. Decrease logging with the `--quiet` flag.
@@ -134,3 +138,7 @@ Feel free to contribute to the codebase, issues and code welcome.
134
138
  ## build pipeline
135
139
 
136
140
  `@normed/bundle` is bootstrapped by being built from typescript to javascript first (using `tsc`, output to `dist`), then using the javascript output to build the original source (output to `bundles-a`), then using that output to build the original source again (output to `bundles`), and finally the last two outputs are compared to ensure they are the same. This acts as a nice little test to check some of the functionality of `@normed/bundle`.
141
+
142
+ # Potential errors
143
+
144
+ es-build, which is essentially the basis for this whole thing, breaks reproducible builds as it includes the full path to a file as both a comment and a map key. To get around this we manually replace certain paths on build. There is a good chance this will not work for globally installed modules and will break certain hard coded strings.