DEV Community: Louis Grenard

Sharing Our Journey Developing the Leon CLI

Louis Grenard — Sat, 05 Feb 2022 14:10:25 +0000

👋 Hey all, the first release of the Leon CLI has landed a few days ago. I'd like to let Divlo and Arthur share their experience building it, the problems they faced, how they solved them and whatever they would like to share with you!

If you are not familiar with Leon yet, Leon is an open-source personal assistant. He is based on Node.js for the core, and uses Python for his modules (skills). Therefore, several requirements need to be installed to start to fully enjoy the experience.

Installing these requirements can be a hassle, origins of several issues you reported were due to their setup. Knowing that we all come from different backgrounds, it may be troublesome to get through this. So we have thought of a CLI to get your own Leon running in 3 commands.

How the Project is Organized

The two companions (us, Divlo & Arthur) started working together with common goals:

Make the installation easy
Cross-platform
And the most important of all, do it well

You guess it, many discussions were needed to have a proper plan (come and join us on the discord server, it's kinda cool there).

Split the tasks, a system to maintain good quality, creating automation, manage our time... So many choices and only one pair of brains.

Once upon a time a brainstorm, a really sweaty one!

How many features should we release? The minimum, we would not want to confuse our friendly Leon users with unnecessary steps.

Even with a few features, we had our whole package of difficulties. Fortunately, we had a well-structured task management system:

Trello for the roadmap.
Discord to communicate, do pair-programming and communicate with the community.
GitHub to host our dear open-source CLI and discuss about implementation inside Pull Requests.

Tech Stack

You asked for the tech stack? This one is tricky...

From the beginning, the very first idea that emerged was to develop the CLI with JavaScript using Node.js to allow as many people as possible to contribute. For maintaining purpose and also personal preferences, our heart led us to TypeScript. You could argue with that choice but try it, you'll be convinced in no time 😉

The next decision was the main library to build the CLI. A classic would be Commander but it had a big drawback for us: the structure. Our goal was to start small and progressively tend to a full-featured tool, the companion for our Leon journey. Commander would allow a nice start but leads us to a kind of messy project as most of the command parameters are inside a single file.

Let us introduce another alternative: Clipanion, a type-safe CLI library with no runtime dependencies, made with TypeScript.

A special thanks to Sindresorhus. Many of our struggles have been solved by his numerous packages, including:

execa to execute commands.
chalk for the tasty flavour in your command line interface (it adds color).
conf to let the CLI persists some data (configuration files and logs).

Technical Challenges

We offer two ways to install Leon:

A classic installation (directly installed on your machine).
With Docker (an independent container).

Two options and two brains, a perfect match! Naturally, we divided the work:

Divlo started on the Docker install.
And Arthur the classic one.

Let's dive into some experience feedback:

Divlo: The command leon create birth was the hardest command to get it working as it's completely cross-platform, so we needed to create Virtual Machines to test on multiple OSes. The Docker installation was a little bit easier, as Docker does the "heavy lifting" for us.
We both learned a lot building this first version of the CLI, but it's only the beginning and we want to make it more and more useful to be the companion for your Leon journey.

Arthur: Leon's CLI is a proof that nothing beats a challenge to learn and exceed your skills. I probably lost some hair managing the cross-platform side... So, I hope the community will appreciate my dedication.
Jokes aside, it's one of the most interesting project I worked on. Enjoy using it!

Scalability

How to easily add features without breaking existing ones? With a stable and trusted architecture.

We started to talk about it before: Clipanion. But it's not the answer to everything... We also needed to reuse features between commands. The object-oriented architecture and the services to isolate our functions per domains were a part of the answer.

To adapt to everyone and every architecture, each command has its set of options.

The next step for scalability is the testing system! For this v1, supporting Windows, Linux and macOS was the biggest challenge in terms of testing and scalability, by far.

Testing

We used a common strategy, a combination of unit testing and end-to-end testing. Knowing that the specificity of our project is to have the OS as the kernel, the end-to-end tests are the most important, they are the guardian of our stability.

Scenarios are the same on each OS and are executed on independent machines:

Retrieve the CLI
Make Leon alive by getting all its dependencies using leon create birth command

Start Leon with leon start and verify that the interface is available

To ensure that the code remains at the top quality and that new features never breaks older ones, we implemented Continuous Integration. It means that every time we (or you) push new lines of code to the CLI, all the tests are executed through GitHub Actions.

What to Expect in the Future

A lot of stuff is coming, our ideas never end. Not only our ideas, yours too. 🙂
Feel free to post any idea you have here.

A non-exhaustive list of incoming features:

leon info to get information of our Leon instances
leon update to obviously update Leon and see him evolve (get the latest features)
A better developer experience for the creation of modules / packages
Easily modify the configuration of Leon (text-to-speech, speech-to-text...)

I Ran Away From Open Source

Louis Grenard — Tue, 21 Dec 2021 13:33:24 +0000

👋 Hey all, I mentioned in the previous blog posts that I'd share the reasons of my missing over the last few years, the vision I have for Leon, your open-source personal assistant, and more about what is going through my mind. So now is the time, let's get started!

I Lost Focus

In June 2019 I released the second beta version of Leon. On that moment, I was in a dynamic mindset that I wanted to build anything I had in mind. It was not exclusive to Leon. I went to bed, keep thinking about solutions to solve problems I was facing in life.

I discovered the IoT world via my work on that time. It was fascinating. I love the whole concept of it. Building scalable architecture and most of all: pressing virtual or physical buttons to trigger actions that create physical impact on the other side of the globe.

Back in time, I created our own IoT pipeline using Microsoft Azure. I built the PKI to deliver and verify devices certificates. It was possible to control devices (send messages, invoke methods, etc.) from a web browser to the device. And it was also possible for devices to request the cloud and handle millions of connections thanks to the IoT hub and device provisioning service. All the data were handled via a stream analytics processor and landed into a data lake like CosmosDB and can also replicate important data to a PostgreSQL one if necessary. The main protocol between our cloud and devices was AMQP, but MQTT was also supported.

At that time, I wanted to build anything that was going through my mind, everyday. Well, we can say I lost focus. In such interesting and noisy world where there are infinite of possibilities, staying focus is maybe one of the hardest thing to do.

My Missing

On top of that, I was questionning my career. I wanted to explore new horizons.

Also, having a girlfriend with an entrepreneurship mindset does not help. I wanted to show her real results. We all know how challenging it is to express what we are doing or share what we are able to do with someone who isn't in the tech industry.

So I got trapped into the ego building circle...

Here is a list of the major things I did during my missing and the benefits I got for each of them:

2aud.io

I built a SaaS that converts URLs (web scraping), documents and text files into audio.

It was supporting 159 types of voice and 30 languages. I launched the private alpha version, collected feedback, got 230+ emails on the waiting list. Then I stopped for whatever reason.

What's cool here is I may inject the core of 2aud.io into a Leon module. So Leon could read any resource for us like a podcast.

Benefits: strengthen my A to Z building skill.

YouTube Videos + Community

I published web development videos on my French YouTube channel, started a Node.js course by going in depth but with a language that everyone can understand, etc.

Around that I put together a community with a Discord server. Today there are still 670+ applications lining up...

In that community people started to build projects together to learn more about web development. I'd say 33% of the people where changing their career path to software engineering. It was composed of people with good experience and newcomers in the tech industry. This variety of profiles created interesting discussions.

People were sharing their projects progress during monthly calls we were organizing. We were warmly welcoming new fellows with proper calls too.

And we were working on our own projects during some immersive call sessions. The idea was to work during an hour in a row by muting microphones. Then we enabled back the mic to share our last hour progress and help each other if necessary for a few minutes. Then we kept going.

Stay tuned because I'd love to recreate the same model of community but around Leon! If you are interested in that then feel free to subscribe to the newsletter.

Benefits:

Learned how to build a private and active community from the green grass.
Learned video making and video animation.

Computer Vision

In December 2020, I challenged myself to learn a bit about computer vision within two days. To get started with this field that was new to me I trained a deep learning model that was recognizing rubik's cubes.

Then I created a PoC that was recognizing shapes on a whiteboard in the purpose of generating a UIDL to automatically create web components.

Well, waaay more data were needed and my time was very limited so the model wasn't super accurate.

Benefits:

Improved my learning skill.
Today Leon has ears and mouth, why not add eyes later on? :)

Every benefit listed above will definitely help in my Leon journey.

In 2020 I also ran a French web agency with a friend on the side of my job and mainly worked on a streaming platform with a customer who is managing French celebrities. Then I started to create a mobile application with React Native to help a relative. Here too, my React Native experience will help Leon growth, I let you think of the possibilities... Hence, by coming back on Leon, I migrated nodes (docs from VuePress to Docusaurus; the website from Nuxt.js to Next.js and this blog from Hexo to Gatsby) to the React ecosystem.

I tried and learned many new things along the way. However, I knew my ultimate goal was to get back on track with Leon and make sure that I'm not missing anything I would like to explore more.

You know what my biggest fear is? It is to be on my death bed, look back and regret to not even try and accomplish my goals. Sooner I realized it is not by focusing on so many things like this that I'm gonna escape that fear.

Today I'm glad to say that I joined the Alibaba Group on the Lazada business several months ago. Don't worry, this does not mean I will have less time to work on Leon. Back in time, I was able to release the first beta version of Leon by having my full-time job. Organization is key.

I Found Back my Whys

I needed to refocus on the why of Leon before to refocus on the technical part. Why am I creating Leon? Why did I even get started at the first place?

Here is how I see it: there is a practical why, and a deep why.

Practical Why

This why is specific to the project itself. What problems is Leon solving?

The answer of this why is the value/result of what the outside world will see and use. You can take a look at the motivations here. And you can continue to read to the next section to know more.

Deep Why

This one is a bit more personal. It is my source of energy to solve the practical why. It is the fuel of my practical why.

To answer, I'd say:

I like solving problems, but most importantly the "how" I solve them is what makes me move forward. This is not specific to programming. It also requires talking with people, doing some so-called "marketing", designing, overall thinking, and more.
Sharing your creations with the world is so exciting because you can let your blueprint behind you. The tech industry is very pleasant for that: you face an issue, you think of a way to solve it, then you can "quickly" build something to fix it and share it.
Having my own vision and driving towards the direction that I have chosen allows me to discover and learn new fields.

Vision for Leon

Earlier this year I questionned myself to get back on track:

What I dream of for Leon is that we can interact with him via different clients (mobile, desktop, customized hardware, etc.). Today with the growth of voice and NLP technologies, it becomes way more accessible to create powerful personal/virtual assistant.

With my IoT experience, I will also bring this field to Leon so we can do home automation and more.

I'd like to bring a social aspect too. At the moment I prefer not to disclose this part.

We can even imagine of using AR and/or VR, but that is a long term thing.

The whole idea is that Leon becomes your virtual brain so he can handle all your virtual troubles and makes you feel that the technology disappears somehow.

Focus

To do so, here are the big lines:

The core of Leon needs to be more powerful. So I will be focusing on this part from now on. Like a way to easily support multi languages, create widgets, add support of JavaScript modules, etc. Check the roadmap to see more.
Leon needs to cover most of the basic use cases of existing closed source assistants.
Growing the community. I paused the project for too long. And without an active community, Leon cannot grow fast. I want to put together a special community of creative people like I mentioned earlier in this post.
I have some ideas in mind that will make Leon smarter. But I will keep those in the private roadmap at the moment and disclose them when the time comes.

Along with the vision, a rebranding was necessary to have a atmosphere that aligns with the vision of Leon. You can take a look at a preview of the new landing page here. In a next blog post I'll talk more about this rebranding. Explaining the reasons behind the "outter space" atmosphere and more...

Wrap Up

With all that said, the direction of Leon is quite clear. I've been missing working on Leon so much! Today we can start again and move forward in a healthy way. Also, I'd like to use this moment to thanks all the sponsors and Vercel for recently sponsoring Leon 🖤

It feels good to be back!

I recently opened my GitHub Sponsor so you can now sponsor me on GitHub and get some perks.

Leon Open-Source Personal Assistant: Getting Rid of Dust / 1.0.0-beta.4

Louis Grenard — Sat, 01 May 2021 16:05:41 +0000

👋 Hey all, the time has come... Like finally! I know it has been a long time. The project has been paused for about 2 years. We'll talk about the reasons of this endless pause in another blog post.

Today, we'll focus on the new release of Leon and understand what's new, where the project is leading to and the thinking process behind some decisions.

Main Focus

The focus of this release is quite obvious. 2 years pause on a project requires a deep work on:

Rethinking about the project vision.
Redefining who would be interested in the project.
Analyzing technical debt and taking action.

At least that's how I put it together.

It's important to mention that the work here was not only technical. I needed to refocus on the WHY of Leon.

Why did I build Leon at the first place?
What problems is it solving?
Is it still valuable today?

Let's focus on the technical part as the other part will be covered in another blog post.

Dependency Updates

That is what happens when you don't update your project dependencies for about 2 years... Let images speak for themselves.

After a `npm install`

After a `npm run build`

How The Commit History Looked Like...

I believe you got a rough idea of what needed to be done. Clearly I updated all dependencies that Leon relies on. Of course I could make use of tools such as Dependabot but I preferred to update everything manually. It allowed me to have a better control of what I was doing and see if each dependency still has its seat in the project. Most of all, and this is only my own opinion, I prefer to keep dependency updates as a one-shot task instead of having noises in pull requests.

I read the changelog of each dependency to understand what has changed, has been improved and check if there was any breaking change.

You can find a list of all the updates here.

Dropping Husky

Leon was using Husky that was triggering a script I wrote to parse a commit message on the commit-msg Git hook.

It was working pretty well after the update, but GUI clients like GitKraken was not working properly anymore due to their recent changes (it was working well before). So I decided to drop Husky or any Git hook trigger script because I don't want this be a bottleneck for contributors. So I keep it simple without commit restriction.

I believe that the CONTRIBUTING.md file is enough to understand how to commit to the project. However, it's quite important to respect the commit convention as it eases the changelog generation for each new release.

Dropping Babel?

While Babel is an awesome JavaScript compiler, I was considering to drop it. Leon does not need to be ahead of current specifications, I felt it was a good choice to drop dependencies related to Babel as it'd lighten the dependency tree (which means faster install, less maintenance work and less potential security issue).

Moreover, since Node.js 14 we can make use of experimental ECMAScript modules which are the official standard format to package JavaScript code for reuse. Node.js was only supporting CommonJS (CJS) modules before that.

But here is the thing, I want to continue to use the module-alias npm package as I find it brings better readability of the imports. I found that it requires to build a custom module loader to resolve it. I concluded that it was too much steps to achieve for a small output, then I chose to postpone the Babel dropping task. If you are interested into that specific case, there is an ongoing GitHub issue.

I might come back to this task once the ecosystem will be more ready.

Raspberry Support?

Thanks to the last changes, apparently Leon might work on at least Raspberry 3B+ as per this comment. A deeper look will be provided on this side.

Feel free to contribute.

Fix Hotword Detection

Leon uses Snowboy for its hotword detection. Unfortunately the project has been discontinued and is suffering from the lack of maintainability.

Indeed, Snowboy uses node-pre-gyp which helps to publish and install Node.js C++ addons from binaries. So when a new Node.js version is shipped, node-pre-gyp must update its listing of the supported targets by specifying the:

New Node.js version.
Node.js C++ ABI number.
The V8 JavaScript engine version.

Usually it is done through this file.

Despite the lack of maintainability, I decided to create a fork of Snowboy and maintain it independently. On this fork, Snowboy works with Node.js >= 14 as specified in this issue comment.

Please keep in mind that is a temporary solution as this part of Leon should be improved in the future. If you have any suggestion for a hotword detection alternative or wish to build one, don't hesitate to shoot me an email at louis.grenard@gmail.com.

I found some alternatives such as Porcupine from Picovoice that works pretty well. But at the moment I'm writing this, their tooling does not allow to have short hotword like Leon. Which is in fact a best practice, but it means we'd need to comply such limitations.

There is More...

The points above were the main ones to focus on for this release. But there are actually more things coming with it!

The Web App is Now Powered by Vite

I'm happy to say that Leon's web app is now powered by Vite. The web app will get major changes in the future, so a review was necessary before to kick off the work.

The web app was using some Node.js features and Browserify. This is an unnecessary layer in our case. I wanted every feature be natively supported by the browsers as upcoming clients will also be natively supported by their respected platform.

Now that we are on an explicit browser compatible codebase, this is where Vite enters the game. In sum: better DX and performance.

Learn about the benefits here.

From CircleCI to GitHub Actions

Until a while I was always using CircleCI for my projects as I think it is doing a great job for CI and CD.

However, since GitHub has launched GitHub Actions I liked the idea of having the codebase close to the CI, so we don't need to get out of the GitHub ecosystem.

Sometimes on CircleCI, Leon was having troubles since the Node.js 14+ upgrade from the Leon's CI Docker image. The same Docker image was finishing all the jobs perfectly on different machines but not on CircleCI ones. It was timing out or finishing with an error for the end-to-end modules tests. The error was related to the Node.js child process that did not work. So my bet is it was sometimes running out of memory.

Since I migrated to GitHub Actions, none of these happened. As Leon was using the Docker type on CircleCI, it looks like there is bit more hardware power on GitHub Actions. I did not try with the raw CircleCI Linux types as I wanted to use the Leon's Docker image dedicated for its CI.

CircleCI

GitHub Actions

Today Leon's CI is composed of 3 GitHub Actions workflows:

build: to ensure Leon can be built successfully.
lint: to ensure the source code is written as per the standards of the project.
tests: to ensure the quality of the features.

If you are interested in migrating from CircleCI to GitHub Actions, GitHub has put together an article that is pretty straightforward.

From Express.js to Fastify

Leon needs an HTTP server to allow clients to grab some metadata such as the version, language, etc. and for more in the future... This is also where the WebSocket handshake happens to establish a bi-directional connection with clients.

Most of the time we hear about Express.js because it is a well established web framework in the Node.js ecosystem, since the early days. But Fastify also joined the OpenJS Foundation which means it is also serious.

I agree with most of what is explained in this article.

Thanks to the great job from Divlo, the migration is shipped with this new release.

Try Leon with a Single-Click

You can try Leon with a single-click thanks to Gitpod.

It will automatically setup an environment with all the requirements and run an instance for you. It allows potential contributors to get started pretty fast and add value to the project.

You can try it here.

Again, kudos to Divlo for suggesting and making this happens 👏

Force Minimum Node.js Version

To ensure that the minimum Node.js and npm versions are respected, the following has been added to the package.json file:

"engines": {
  "node": ">=14.0.0",
  "npm": ">=5.0.0"
}

New NLP

Since the previous release, NLP.js pushed a lot of work and has released a major version, moving from a monolithic library to multiple independent packages. So I spent some time to make Leon's NLP compatible to the latest changes.

These changes mostly include the NER and NLU of Leon and still makes use of neural network.

Always More...

Please feel free to take a look at the roadmap to have a full understanding of what has been done for this release.

Breaking Changes

This release includes a few if it's nearly none breaking changes:

Have I Been Pwned module: it now requires a key to be able to request their API.
IBM Watson: IBM will shutdown their legacy API (end of life on 26 May 2021). Leon complies to the last changes of the IBM Watson Node.js SDK. If you are using Watson TTS or Watson STT, you can make the changes as specified in the docs.
Amazon Polly: Amazon did a complete modular rewrite of their Node.js SDK. Leon complies to these changes. If you are using Amazon Polly, make sure to pull the last configuration file structure for Amazon Polly.

What's Next

Long Term

In the long term, an important guideline needs to be followed so Leon can shine better:

Drastic improvements need to be done on the foundations/core and the tooling sides. That includes context in modules, JavaScript bridge so we can write JavaScript modules, widgets for better looking module outputs, dynamic multi-languages support on edge, new clients and so on...
Then we hope we can grow the community bigger thanks to what Leon will be able to do.
Scale Leon with new useful modules.
The idea is to get closer and closer to closed source assistants thanks to the growing community and better foundations. But by ALWAYS keeping the core open and a flexibility that challenges our imagination.

Shorter Term

In a shorter term, here is what we can expect to see:

A blog post explaining my Coming Back on the project, the WHY and things I mentioned earlier. It's important for me to share you my thoughts and this journey.
A full rebranding with a new visual identity of the project that reflects more the values and vision of Leon.
The CLI so it improves the onboarding experience by removing the hassle of the requirements, centralizing commands and more... Kudos to Arthur and Divlo who are working on it! 👏
Take a look at the roadmap to see more.

Cheers 🍹,
Louis (@louistiti_fr)

HTTP Response Status Codes In Real Life 😅

Louis Grenard — Mon, 24 Feb 2020 01:40:46 +0000

Hello world!

A few days ago I was wondering how HTTP response status codes would look like in real life.

I picked up my camera and tried to implement them around me.

Well, it was an interesting experience!

Here is the YouTube video with these guys implemented:

The Story Behind Leon

Louis Grenard — Sun, 17 Feb 2019 13:06:13 +0000

This post was firstly published on the original blog.

Big disclosure: I never watched the movie Léon: The Professional (at least not yet).

Who Am I

👋 Hey all, my name is Louis Grenard, I was born in the 90's in the French mountains. I'm currently living in Shenzhen, China and working at a great company called NOA Labs.

I love building things since my early years, turning my GAN356 Air SM and I truly believe in open-source.

Who is Leon

Let me explain you in few words.

Leon is an open-source personal assistant who can live on your server. He does stuff when you ask for it.

You can talk to him and he can talk to you. You can also text him and he can also text you. If you want to, Leon can communicate with you by being offline to protect your privacy.

Why The Hell "Leon"

Leon is pretty simple to remember as a name and it is easier to pronounce whatever the language (Leon in English, Léon in French, Lái áng in Chinese, León in Spanish, etc.). Moreover, Leon is created from Leo which means lion and that is my astrological sign.

Timeline

End of 2016 — Let's get back to the end of 2016. Mark Zuckerberg, the Facebook CEO published a note and a video about his 2016 personal challenge. I was very exciting about the idea of interacting with a tech system by voice. Of course virtual assistants such as Siri already exist on that time, but the fact of reading about and seeing the Zuck's assistant gave me the desire to know more about it.

Few days later I was on a train on my way back to my dear hometown in France. I quickly grabbed my laptop, and started coding a proof of concept in an HTML file. My very first motivation was to understand how the speech-to-text and text-to-speech were working in web development, so I naturally implemented the Web Speech API and few hours later I got my PoC done.

Early 2017 — A few months later I was on my way to attend a family event in Munich, Germany and I was thinking about doing more than a simple web speech PoC. Something that could help in my daily life. I remember the first feature idea was a financial tracker, I was thinking it could be so cool to say:

Leon, how much money did I spend in restaurants in 2016

And have something that reply me by voice and text with few details. So I caught my phone and started to write some feature ideas.

Mid-2017 — At the end of June 2017 I moved to China and began my full-time job here. Watch was clocking and it's only in October that I decided to make a plan to properly work on Leon besides my work. I committed on a private repository the 4th of November 2017.

Few weeks later I was thinking if Leon helps me, then it might also help others. So I decided to create a modulable architecture and with a module that download videos from YouTube to save them on the device. I wanted that module because on that moment I was living 1 hour from my work and I needed to take subways, so I could watch/listen tech videos and podcasts during that time.

Early 2018 — It is the 7th of January 2018 I created the Leon's roadmap by setting up some cards such as this one and started to document myself about open-source ecosystems (I highly recommend you Open Source Guides). On that time, here is how Leon looked like:

March 2018 — Then personal problems came out, and I did not work on Leon for two months. It's only in March 2018 that I wanted to test if Leon is interesting not only for me, but also for others. So I made some researches about Reddit, how it exactly works, the rules, etc. And I end up by creating a teasing video and publish it to several subreddits, such as /r/Python, /r/javascript, etc. I received tons of feedback, and got an issue because I published the video on Google Drive, and the video reached the maximum views allowed in a short period, so I needed to quickly publish the video on YouTube. On that moment, Leon was still using the Web Speech API, so I refactored by implementing things that you know with the first release.

Mid-2018 - now — We are now in August 2018, where I decided to take a break due to other personal problems. Then it is from November 2018 I caught up with Leon until the release 🎉.

If I compile the total of working time I spent on the Leon's 1.0.0-beta.0 release. The result is 11 months, that includes: week-ends, early morning during weekdays (between 6am to 8am) before starting my lovely full-time work, and also at the end of the day after gym. And of course this result also includes days out of the computer. This number represents the whole timeline and not the specific time I was purely working on Leon. The number of commits on the private repository is 438.

Thanks

Please wait! It's not the end yet, I just want to thanks now because I think it's more accurate to write it right after the above section.

I use these few lines to warmly thanks my:

Family for having supported my long speeches about Leon and seeing me canceled some family events.
Lovely girlfriend for giving me such energy and motivation.
Friends who suggesting ideas and believing in Leon since his early days.

💙

After One Week

I released Leon under the 1.0.0-beta.0 version the 10th of February 2019. Today we are now one week later than the release. Let me share what's happened over this week but before that, please... Let me tell you that you are incredibly A.W.E.S.O.M.E!

Leon has been well welcomed and all of that prove Leon has potential and there is a lot to do, together. My friends, it's an amazing adventure which is starting over here!

Here are some numbers from the initial release:

24 hours later — Leon gets his first 100 GitHub stars and appears in the GitHub JavaScript trending page.
48 hours later — Leon reaches 200 GitHub stars.
4 days later — Leon has more than 400 GitHub stars.
5 days later — Someone published Leon on the well known Hacker News and it has been well received. That brings Leon on the front page, to the 3rd position for few hours, then the 10th position for a complete day.
6 days later — The Leon's repository is ranked at the 1st position of the main GitHub trending page.
7 days later (today) — Leon has more than 1.7k stars.

What's Next

The numbers above are promising, that's great and thanks to all of you for supporting the project. However, there is a lot upcoming, this first release is the foundations of Leon.

I already set the next milestone which is the 1.0.0-beta.1 version. Now, Leon needs to grow up, he is only one week old. I count on you for contributing.

DEV Community: Louis Grenard

Sharing Our Journey Developing the Leon CLI

How the Project is Organized

Tech Stack

Technical Challenges

Scalability

Testing

What to Expect in the Future

I Ran Away From Open Source

I Lost Focus

My Missing

2aud.io

YouTube Videos + Community

Computer Vision

I Found Back my Whys

Practical Why

Deep Why

Vision for Leon

Focus

Wrap Up

Leon Open-Source Personal Assistant: Getting Rid of Dust / 1.0.0-beta.4

Main Focus

Dependency Updates

After a npm install

After a npm run build

How The Commit History Looked Like...

Dropping Husky

Dropping Babel?

Raspberry Support?

Fix Hotword Detection

There is More...

The Web App is Now Powered by Vite

From CircleCI to GitHub Actions

From Express.js to Fastify

Try Leon with a Single-Click

Force Minimum Node.js Version

New NLP

Always More...

Breaking Changes

What's Next

Long Term

Shorter Term

HTTP Response Status Codes In Real Life 😅

The Story Behind Leon

Who Am I

Who is Leon

Why The Hell "Leon"

Timeline

Thanks

After One Week

What's Next

Spread The Word & Stay Tuned

After a `npm install`

After a `npm run build`