Now that Indium 2.0 is around the corner, it’s about time to write this post!
About Indium 2.0
Indium 2.0 is not out yet, but if you’re installing Indium from MELPA, you’re already using it.
New project configuration
New client/server architecture
The new Indium will also be based on a client/server architecture, and will require the installation of the indium server like the following:
npm install -g indium
You can read the documentation of the new TCP protocol here.
As a result, Indium will be much more responsive.
Setting up Indium
Let’s start with the creation of a React project built with the CLI tool
sudo npm install -g create-react-app create-react-app my-app cd my-app npm install npm start
We need to tell Indium how to connect to our new project
my-app. To do
that, let’s create a
.indium.json file at the root of the project:
We only need one configuration, but Indium supports any number of configurations per project, including mixing NodeJS and Chrome.
Firing up Indium
To start Indium, you can either do
M-x indium-connect to connect to a running
M-x indium-launch to
start a new process and automatically connect to it.
For more information about setting up and starting Indium, read the Getting up and running section of the documentation.
The new architecture of Indium is brand new, and I expect issues to be discovered. You can open issues on the GitHub issue tracker (please do!).
If you are unsure how to best report an issue for Indium, there’s a section in the manual for that!