How to make an import available on scala-cli repl start up

spamegg1 · December 23, 2024, 6:20am

This is a requested feature:

Feature initImportREPL: allow initial imports to be automatically available in repl session

opened 09:18AM - 13 Feb 24 UTC

enhancement UX REPL

## **Is your feature request related to a problem? Please describe.** It is t…edious and annoying to have to retype `import allthethings.*` everytime I start the repl with `scala-cli --repl .` ## **Describe the solution you'd like** I would like a way to state what initial imports I want to directly access in all repl sessions of the current build. It should be able to do this both with a using-directive and a command-line option. ## **Describe alternatives you've considered** A more general solution is to provide the corresponding feature of sbt's `console / initialCommands` which would be more powerful. In sbt you write for example: ```scala console / initialCommands := "import mypack.stuff.*, otherpack.morestuff.*" ``` I have tried using the scala-cli option `--scala-snippet` but that does not work with scala-cli version 1.1.2 as it gives this warning and ignores the import: ```scala $ scala-cli repl . --scala-snippet "import reqt.*" Starting compilation server Compiling project (Scala 3.3.1, JVM (17)) [warn] ./.scala-build/reqT-solver_6554fc5f28-77219591e6/src_generated/main/scala-snippet.scala:1:1 [warn] No class, trait or object is defined in the compilation unit. [warn] The incremental compiler cannot record the dependency information in such case. [warn] Some errors like unused import referring to a non-existent class might not be reported. [warn] import reqt.* [warn] ^^^^^^^^^^^^^ ``` ## **Additional context** This has been discussed in both #604 and #2185 - the latter has a wider scope.