Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

elm-tooling-cli v1.15.0 #122

Merged
merged 1 commit into from
Sep 30, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,19 @@
### Version 1.15.0 (2023-09-30)

> ℹ️ If you use macOS ARM (Apple Silicon) and have used `elm-tooling` 1.11.0–1.14.1 before, you need to clear previously downloaded binaries in order to get the newest macOS ARM binary. Otherwise you’ll keep using the one from 1.11.0.
>
> ```bash
> # Remove downloaded binaries:
> rm -R ~/.elm/elm-tooling/elm/0.19.1/
> # Install new binaries:
> cd your-project
> npx elm-tooling install
> ```

- Changed: Different macOS ARM (Apple Silicon) binary for elm 0.19.1.

The previous macOS ARM binary could sometimes segfault while installing Elm packages. This was fixed by Evan upgrading the Elm compiler to a [newer GHC version](https://github.com/elm/compiler/commit/0421dfbe48e53d880a401e201890eac0b3de5f06). He then uploaded a macOS ARM binary to [official Elm 0.19.1 release](https://github.com/elm/compiler/releases/tag/0.19.1). This version of `elm-tooling` downloads a copy of that binary.

### Version 1.14.1 (2023-09-09)

- Fixed: The TypeScript type definitions shipped in the npm package are now more correct. Previously they used `export default`, but apparently `export =` is the correct syntax to use for packages that export a single function, which can be used both in CJS and MJS. (Read more about [Incorrect default export](https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/4706e9a84892be17888bb01a4d85c0bfed3230c2/docs/problems/FalseExportDefault.md)). It should now be possible to do `const elmToolingCli = require("elm-tooling")` in a `@ts-checked`ed JS file without TypeScript complaining.
Expand Down
2 changes: 1 addition & 1 deletion docs/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ With the above steps, you might end up with changes like this:
"devDependencies": {
- "elm": "0.19.1",
- "elm-format": "0.8.3"
+ "elm-tooling": "1.14.1"
+ "elm-tooling": "1.15.0"
},
"scripts": {
+ "postinstall": "elm-tooling install"
Expand Down
2 changes: 1 addition & 1 deletion example/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package-real.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "elm-tooling",
"version": "1.14.1",
"version": "1.15.0",
"author": "Simon Lydell",
"license": "MIT",
"description": "Manage elm-tooling.json. Install Elm tools.",
Expand Down