|
1 | 1 | # Changelog
|
2 | 2 |
|
| 3 | +## 💫 0.3.0 |
| 4 | + |
| 5 | +### ✨ Features |
| 6 | + |
| 7 | +- **Logging - [mgattozzi], [pull/134]** |
| 8 | + |
| 9 | + Up until now, we've forced folks to rely on emoji-jammed console output to debug |
| 10 | + errors. While emojis are fun, this is often not the most pleasant experience. Now |
| 11 | + we'll generate a `wasm-pack.log` file if `wasm-pack` errors on you, and you can |
| 12 | + customize the log verbosity using the (previously unimplemented) verbosity flag. |
| 13 | + |
| 14 | +[pull/134]: https://github.com/ashleygwilliams/wasm-pack/pull/134 |
| 15 | + |
| 16 | +- **`--target` flag - [djfarly], [pull/132]** |
| 17 | + |
| 18 | + `wasm-bindgen-cli` is able to generate a JS module wrapper for generated wasm files |
| 19 | + for both ES6 modules and CommonJS. Up until now, we only used wasm-bindgen's default |
| 20 | + behavior, ES6 modules. You can now pass a `--target` flag with either `nodejs` or |
| 21 | + `browser` to generate the type of module you want to use. Defaults to `browser` if not |
| 22 | + passed. |
| 23 | + |
| 24 | +[djfarly]: https://github.com/djfarly |
| 25 | +[pull/132]: https://github.com/ashleygwilliams/wasm-pack/pull/132 |
| 26 | + |
| 27 | +- **human readable panics - [yoshuawuyts], [pull/118]** |
| 28 | + |
| 29 | + Panics aren't always the most friendly situation ever. While we never want to panic on ya, |
| 30 | + if we do- we'll do it in a way that's a little more readable now. |
| 31 | + |
| 32 | +[pull/118]: https://github.com/ashleygwilliams/wasm-pack/pull/118 |
| 33 | + |
| 34 | +- **typescript support by default - [kwonoj], [pull/109]** |
| 35 | + |
| 36 | + `wasm-bindgen` now generates typescript type files by default. To suppress generating |
| 37 | + the type file you can pass the `--no-typescript` flag. The type file is useful for more |
| 38 | + than just typescript folks- many IDEs use it for completion! |
| 39 | + |
| 40 | +[kwonoj]: https://github.com/kwonoj |
| 41 | +[pull/109]: https://github.com/ashleygwilliams/wasm-pack/pull/109 |
| 42 | + |
| 43 | +- **wrap `npm login` command - [djfarly], [pull/100]** |
| 44 | + |
| 45 | + In order to publish a package to npm, you need to be logged in. You can now use |
| 46 | + `wasm-pack login` to login to the npm (or any other) registry. |
| 47 | + |
| 48 | +[pull/100]: https://github.com/ashleygwilliams/wasm-pack/pull/100 |
| 49 | + |
| 50 | +- **exit early on failure - [mgattozzi], [pull/90]** |
| 51 | + |
| 52 | + Until now, `wasm-pack` would continue to run tasks, even if a task failed. Now- if something |
| 53 | + fails, we'll exit so you don't have to wait to fix the error. |
| 54 | + |
| 55 | +[pull/90]: https://github.com/ashleygwilliams/wasm-pack/pull/90 |
| 56 | + |
| 57 | +### 🤕 Fixes |
| 58 | + |
| 59 | +- **force install wasm-bindgen - [ashleygwilliams], [pull/133]** |
| 60 | + |
| 61 | + Using an out of date version of `wasm-bindgen` can run you into a bunch of trouble. This |
| 62 | + very small change should fix the large number of bug reports we received from users using |
| 63 | + an out of date `wasm-bindgen-cli` by force installing `wasm-bindgen-cli` to ensure the user |
| 64 | + always has the latest version. We don't expect this to be a forever solution (it's a bit |
| 65 | + slow!) but it should help those who are getting started have a less rough time. |
| 66 | + |
| 67 | +[pull/133]: https://github.com/ashleygwilliams/wasm-pack/pull/133 |
| 68 | + |
| 69 | +- **fix CI release builds - [ashleygwilliams], [pull/135]** |
| 70 | + |
| 71 | + This was not working! But now it is! You can always use `cargo install` to install |
| 72 | + wasm-pack, but now you can find pre-built Linux and Mac binaries in the [Releases] |
| 73 | + tab of our GitHub repo. |
| 74 | + |
| 75 | +[Releases]: https://github.com/ashleygwilliams/wasm-pack/releases |
| 76 | +[pull/135]: https://github.com/ashleygwilliams/wasm-pack/pull/135 |
| 77 | + |
| 78 | +### 🛠️ Maintenance |
| 79 | + |
| 80 | +- **remove `quicli` dependency - [mgattozzi], [pull/131]** |
| 81 | + |
| 82 | + While `quicli` is a great way to get started writing a CLI app in Rust- it's not meant for |
| 83 | + large, mature applications. Now that `wasm-pack` is bigger and has many active users, we've |
| 84 | + removed this dependency to unblock further development on the tool. |
| 85 | + |
| 86 | +[pull/131]: https://github.com/ashleygwilliams/wasm-pack/pull/131 |
| 87 | + |
| 88 | +- **update rustfmt CI test - [djfarly], [pull/128]** |
| 89 | + |
| 90 | + Since 0.2.0 how one should call `rustfmt` changed! We've kept it up to date so we can continue |
| 91 | + to maintain conventional style in the codebase. |
| 92 | + |
| 93 | +[pull/128]: https://github.com/ashleygwilliams/wasm-pack/pull/128 |
| 94 | + |
| 95 | +- **custom module for errors - [mgattozzi], [pull/120]** |
| 96 | + |
| 97 | + Thanks to the `failure` crate, we've been playing fast and loose with errors for a bit. We're |
| 98 | + finally getting serious about error handling - by organizing all of our specific errors in a |
| 99 | + specific module. This will make it easier to communicate these errors out and handle new error |
| 100 | + cases from future features. |
| 101 | + |
| 102 | +[pull/120]: https://github.com/ashleygwilliams/wasm-pack/pull/120 |
| 103 | + |
| 104 | +### 📖 Documentation |
| 105 | + |
| 106 | +Special thanks to [data-pup] who continues to be our documentation champion! In case you missed it, |
| 107 | +check out the guides in the [docs directory!](docs)! |
| 108 | + |
3 | 109 | ## 🌌 0.2.0
|
4 | 110 |
|
5 | 111 | This release focuses on filling out all commands and improving stderr/out
|
|
0 commit comments