Jakub Chrzanowski

@prabal-raghav I can confirm that. I use `import 'package'` in my app and `getModuleName` function returns: /home/hsz/Projects/project/src/package instead of package Example input that is passed to the main function: context...

@pgnd We’re constantly improving the quality of JetBrains Marketplace, support, and actual plugins delivered to end-users. Since third-party plugins aren’t our property, we can’t do much about their issues. As...

@pgnd I'm aware of the thread you've mentioned, and still, my answer is valid. Since April, we didn't get any confirmation from the plugin author or any feedback about the...

I was able to get rid of `aws-sdk` package which is nested dependency (production dependency for some of my dependencies) with: ```yaml custom: webpack: includeModules: true packagerOptions: scripts: - rm...

Implemented. Feature will be released in v2.0.0 Demo recording: https://twitter.com/hszanowski/status/1595318733647519744?s=61&t=yPeWEoztW7Q2KC_wgtghQw

With the IntelliJ Platform Gradle Plugin 2.0, the `testFramework.jar` bundled with IDEs is no longer attached to the project — it may be even removed from the distribution in the...

This is now possible with IntelliJ Platform Gradle Plugin 2.0: ```kotlin import org.jetbrains.intellij.platform.gradle.IntelliJPlatformType import org.jetbrains.intellij.platform.gradle.tasks.RunIdeTask tasks { val runPhpStorm by registering(RunIdeTask::class) { type = IntelliJPlatformType.PhpStorm version = "2023.2.2" } val...

The base name will be changed to _IntelliJ Platform Gradle Plugin_ That could automatically lead to the ID change to `org.jetbrains.intellij.platform`

Yes, the repository name can be adjusted as well. GitHub handles redirections nicely, so there won't be any issues here.

As mentioned above, the 2.0 release introduces: - new name: **IntelliJ Platform Gradle Plugin** - new ID: `org.jetbrains.intellij.platform` - new repository name: https://github.com/JetBrains/intellij-platform-gradle-plugin