Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

Running Expo in WSL2

So you want to start a project in Expo, you are running Windows and WSL2, you follow the instructions and create you application like so:

$ npm install --global eas-cli
$ npx create-expo-app myExpoApp
$ cd myExpoApp
$ eas init --id your-id-here

Then as per the instructions on the `readme.md` you run:

$ npm install
$ npx expo start

And you are presented with the following screen:

Great! Let’s scan the barcode and we should be up and running! But, No! You are presented with this:

This is my solution to get around this issue:

$ npx expo start --tunnel

But rather than entering this every time, I update my package.json with an entry for `start-wsl`

$ npm run-script start-wsl

If you are wondering why I don’t just update start to include --tunnel it is because not everyone in my team is going to be using WSL2 and I don’t want to annoy those on Windows without WSL2, nor those on linux or MacOS.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *