{"id":522950,"date":"2024-11-05T14:26:58","date_gmt":"2024-11-05T13:26:58","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=amper&p=522950"},"modified":"2024-11-13T11:32:49","modified_gmt":"2024-11-13T10:32:49","slug":"amper-update-november-2024","status":"publish","type":"amper","link":"https:\/\/blog.jetbrains.com\/en\/amper\/2024\/11\/amper-update-november-2024","title":{"rendered":"Amper Update November 2024 \u2013 Project File Tooling, Compose Resources, KSP2, and Android Release Builds"},"content":{"rendered":"\n

Amper 0.5.0<\/a> is now available! With this release, we\u2019ve improved the IDE experience when working with multiple modules and project.yaml<\/code> files, made nested completion in Amper configuration files more powerful, introduced support for Compose Resources and KSP2, improved Android release builds, and more!<\/p>\n\n\n\n

For the full list of changes and bug fixes in Amper 0.5.0, see the release notes<\/a>.<\/p>\n\n\n\n

To get support for Amper\u2019s latest features, use Fleet 1.42<\/a> or IntelliJ IDEA 2024.3<\/a> (or later versions).<\/em><\/p>\n\n\n\n

Tooling support for working with modules and project files<\/h2>\n\n\n\n

In the previous update<\/a>, we introduced project files for standalone Amper projects. With this release, you\u2019ll now get additional tooling to work with these files.<\/p>\n\n\n\n

When working in the configuration file of a newly created module, you\u2019ll see a warning and a quick-fix that helps you add it to the list of modules:<\/p>\n\n\n\n

Improved nested completion<\/h2>\n\n\n\n

The settings block in Amper files offers nested completion for all of the available values you can configure, letting you easily search for values even if you don\u2019t know where in the structure they\u2019re nested.<\/p>\n\n\n\n

To make this even more convenient, you\u2019ll now get this completion support even when you\u2019re at the top level of a module file:<\/p>\n\n\n\n

Compose resources<\/h2>\n\n\n\n

You can now use Compose Multiplatform resources<\/a> in standalone Amper projects, which allows you to easily access images, strings, fonts, and files in your Compose application.<\/p>\n\n\n\n

settings:\n\u00a0\u00a0compose:\n\u00a0\u00a0\u00a0\u00a0enabled: true\n\u00a0\u00a0\u00a0\u00a0resources:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0packageName: com.example.app\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0exposedAccessors: true<\/pre>\n\n\n\n
Kotlin Symbol Processing<\/h2>\n\n\n\n
The standalone version of Amper now has support for Kotlin Symbol Processing. Many third-party libraries<\/a> use KSP to generate code as part of the compilation process.<\/p>\n\n\n\n
\n
Amper works with KSP2<\/a>, so any processors used must be updated for KSP2 as well. We\u2019re expecting most processors to make this upgrade soon, as KSP1 is deprecated and will no longer be supported in Kotlin 2.1. However, at the time of this release, you might still see some gaps in support, such as issues with native targets.<\/p>\n<\/blockquote>\n\n\n\n
To add a processor to your module, use the settings.kotlin.ksp<\/code> section. You can also specify the options that you want to pass to KSP here.<\/p>\n\n\n\n
settings:\n\u00a0\u00a0kotlin:\n\u00a0\u00a0\u00a0\u00a0ksp:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0processors:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0- androidx.room:room-compiler:2.7.0-alpha09\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0processorOptions:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0room.schemaLocation: .\/schema<\/pre>\n\n\n\n
In multiplatform modules, configuration in the settings block is applied to all platforms by default, including KSP processors. If you need to specify which platforms to run a KSP processor on, use a settings block with a platform qualifier<\/a>:<\/p>\n\n\n\n
settings@android:\n\u00a0\u00a0kotlin:\n\u00a0\u00a0\u00a0\u00a0ksp:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0processors:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0- androidx.room:room-compiler:2.7.0-alpha09<\/pre>\n\n\n\n
Android release builds<\/h2>\n\n\n\n
Amper can now create signed release builds of Android apps in both Gradle-based and standalone Amper projects. These builds will use R8<\/a> automatically, with minification and shrinking enabled.<\/p>\n\n\n\n
To enable signing for release builds, use the new android.signing<\/code> option in the settings block:<\/p>\n\n\n\n
settings:\n\u00a0\u00a0android:\n\u00a0\u00a0\u00a0\u00a0signing: enabled<\/pre>\n\n\n\n
You can provide the signing details by creating a keystore.properties<\/code> file in the module:<\/p>\n\n\n\n
storeFile=\/Users\/example\/.keystores\/release.keystore\nstorePassword=store_password\nkeyAlias=alias\nkeyPassword=key_password<\/pre>\n\n\n\n
There are options available to customize R8\u2019s obfuscation and to change the location of the properties file containing the signing details. Amper can also generate a new keystore for you if you don\u2019t have one already.<\/p>\n\n\n\n
You can refer to the documentation about configuring Android builds<\/a> for more details, and you can also look at samples to see custom Proguard configuration in both standalone<\/a> and Gradle-based<\/a> Amper projects.<\/p>\n\n\n\n
Parcelize support for Android<\/h2>\n\n\n\n
In projects using the standalone version of Amper, you can now turn on the Parcelize<\/a> plugin for Android, using the new settings entry: <\/p>\n\n\n\n
settings:\n\u00a0\u00a0android:\n\u00a0\u00a0\u00a0\u00a0parcelize: enabled<\/pre>\n\n\n\n
This lets you annotate Parcelable<\/code> classes with @Parcelize<\/code> to generate an implementation automatically:<\/p>\n\n\n\n
import kotlinx.parcelize.Parcelize\n\n@Parcelize\nclass User(val firstName: String, val lastName: String, val age: Int): Parcelable<\/pre>\n\n\n\n
As Parcelize is an Android-specific feature, it requires some additional configuration in multiplatform projects, which is described in the documentation<\/a>.<\/p>\n\n\n\n
Updated dependencies and defaults<\/h2>\n\n\n\n
Amper now uses these new versions of dependencies and default values:<\/p>\n\n\n\n