new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Expo & React Native · all subjects

build configuration

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Default eas.json structure created by configuration

The eas build:configure command creates an eas.json file in the root directory with default configuration. For Expo projects, it defines three build profiles: development (with developmentClient set to true and distribution set to internal), preview (with distribution set to internal), and production (empty object). Additional custom build profiles beyond these three can be created.

app.json identifiers required for Expo projects

For Expo projects, if android.package and ios.bundleIdentifier are not already configured in app.json, EAS CLI will prompt you to specify them when you create your first build. The android.package is the Android application ID used to identify your app on the Google Play Store. The ios.bundleIdentifier is used to identify your app on the Apple App Store.

cli.requireCommit option prompts for git commit

If cli.requireCommit is set to true in eas.json, after configuration is complete you will be prompted to commit all the changes made during configuration. You can review the changes before committing and can either specify a custom git commit message or use a default message.

Give your agent this brain