pxt-microbit 4.1.7 → 4.1.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,12 +1,11 @@
1
1
  # WebUSB
2
2
 
3
- [WebUSB](https://wicg.github.io/webusb/) is an emerging web standard that allows to access @boardname@ from web pages.
4
- It allows for a **one-click download** without installing any additional app or software! It also allows to receive data from the @boardname@.
3
+ [WebUSB](https://wicg.github.io/webusb/) is a recent and developing web standard that allows you to access @boardname@ directly from a web page. It allows for a **one-click download** without installing any additional app or software! It also lets you receive data into the web page from the @boardname@.
5
4
 
6
5
  ## Support
7
6
 
8
- * Chrome 79+ browser for Android, Chrome OS, Linux, macOS and Windows 10.
9
- * Microsoft Edge 79+ browser for Android, Chrome OS, Linux, macOS and Windows 10.
7
+ * Chrome (version 79 and newer) browser for Android, Chrome OS, Linux, macOS and Windows 10.
8
+ * Microsoft Edge (version 79 and newer) browser for Android, Chrome OS, Linux, macOS and Windows 10.
10
9
 
11
10
  ## Prepare your @boardname@
12
11
 
@@ -18,13 +17,36 @@ Make sure that your @boardname@ is running version **0249** or above of the firm
18
17
 
19
18
  Here are the steps on the supported browsers:
20
19
 
21
- * connect your @boardname@ to your computer with the microUSB cable
22
- * open a project
23
- * click the triple dot icon on the **Download** button and click **Pair device**
24
- * click on the **Pair device** button and select **BBC micro:bit CMSIS-DAP** or **DAPLink CMSIS-DAP** from the list.
20
+ * Connect your @boardname@ to your computer with the Micro USB cable
21
+ * Open a project
22
+ * Click the triple dot icon on the **Download** button and then click **Connect device**.
23
+
24
+ ![Download button and menu](/static/mb/device/usb/download-button-menu.jpg)
25
+
26
+ * In the connection message window, click **Next**.
27
+
28
+ ![Connect device dialog](/static/mb/device/usb/connect-usb.jpg)
29
+
30
+ * Another message window will display telling you which device you should pair with. Click **Next** to go to the device list.
31
+
32
+ ![Device name dialog](/static/mb/device/usb/pair-dap.jpg)
33
+
34
+ * Select **BBC micro:bit CMSIS-DAP** or **DAPLink CMSIS-DAP** from the list and click **Connect**.
35
+
36
+ ![Device list for WebUSB pairing](/static/mb/device/usb/pair-device.jpg)
25
37
 
26
38
  If you don't see any devices in the list and @boardname@ has the right firmware (**0249** or above), you can create a [support ticket](https://support.microbit.org/support/tickets/new) to notify the Micro:bit Foundation of the problem. Skip the rest of these steps.
27
39
 
40
+ ![Device list for WebUSB pairing](/static/mb/device/usb/no-pair.jpg)
41
+
42
+ * When your @boardname@ is connected, you'll see the **Connected to micro:bit** message window. Click on **Done** and you're ready to go!
43
+
44
+ ![Connected message window](/static/mb/device/usb/connected.jpg)
45
+
46
+ * If the connection to your @boardname@ was unsuccessful, you'll see the **Connect failed** message. You can press **Try Again** to attempt the connection again or cancel the window and [troubleshoot](/device/usb/webusb/troubleshoot) your connection.
47
+
48
+ ![Connect failed message window](/static/mb/device/usb/connect-fail.jpg)
49
+
28
50
  ## Unpair your @boardname@ #unpair
29
51
 
30
52
  You will need to unpair your device from the editor to disable WebUSB.
@@ -33,7 +55,7 @@ You will need to unpair your device from the editor to disable WebUSB.
33
55
  * Uncheck each **BBC micro:bit CMSIS-DAP** or **DAPLink CMSIS-DAP** device
34
56
  * Reload the page
35
57
 
36
- ![](/static/webusb/unpair.gif)
58
+ ![Unpairing from the browser](/static/webusb/unpair.gif)
37
59
 
38
60
  ## One-click Download
39
61
 
@@ -1,32 +1,22 @@
1
- # Uploading from Chrome for Windows
2
-
3
- ## ~ hint
4
-
5
- Starting with Chrome 65 on Windows 10,
6
- you can use **WebUSB** to download with one-click.
7
- [Learn more about WebUSB...](/device/usb/webusb).
8
-
9
- ## ~
1
+ # Transferring from Chrome for Windows
10
2
 
11
3
  While you're writing and testing your programs, you'll mostly be [running them
12
4
  in the simulator](/device/simulator), but once you've finished your program you
13
5
  can **compile** it and run it on your micro:bit.
14
6
 
15
- The basic steps are:
7
+ ## Transfer using a WebUSB connection
16
8
 
17
- 1. Connect your micro:bit to your computer via USB
18
- 2. Click **Download** and download the `.hex` file
19
- 3. Copy the `.hex` file from your computer onto the micro:bit drive
9
+ With Chrome (version 79 and newer), you can transfer your program to the @boardname@ with a single click. If your browser supports WebUSB, you can use the **one-click download** feature to send your programs to the @boardname@. See the [WebUSB](/device/usb/webusb) page to learn how to pair your @boardname@ with a computer and transfer your programs with a single click.
20
10
 
21
- ## Requirements
11
+ ## Downloading your program as file
22
12
 
23
- You need the following things to transfer and run a script on your micro:bit:
13
+ The basic steps are:
24
14
 
25
- * A-Male to Micro USB cable to connect your computer to your micro:bit. This is
26
- the same cable that is commonly used to connect a smart phone to a computer.
27
- * A PC running Windows 7 or later.
15
+ 1. Connect your @boardname@ to your computer with a USB cable (use an A-Male to Micro USB cable)
16
+ 2. Click **Download** and download the `.hex` file
17
+ 3. Copy the `.hex` file from your computer onto the micro:bit drive
28
18
 
29
- ## Step 1: Connect your micro:bit to your computer
19
+ ### Step 1: Connect your micro:bit to your computer
30
20
 
31
21
  First, connect the micro:bit:
32
22
 
@@ -40,7 +30,7 @@ it appears as a new drive under Devices.
40
30
 
41
31
  ![](/static/mb/device/usb-windows-device.jpg)
42
32
 
43
- ## Step 2 (optional): Configure Chrome to ask where to save the file
33
+ ### Step 2 (optional): Configure Chrome to ask where to save the file
44
34
 
45
35
  You only need to do this once.
46
36
 
@@ -49,7 +39,7 @@ You only need to do this once.
49
39
  3. Find the **Downloads** settings.
50
40
  4. Enable the setting **Ask where to save each file before downloading**.
51
41
 
52
- ## Step 3: Download your program
42
+ ### Step 3: Download your program
53
43
 
54
44
  1. Open your project on @homeurl@
55
45
  2. Click **Download**
@@ -57,11 +47,11 @@ You only need to do this once.
57
47
  so save it into the `MICROBIT` drive.
58
48
  Otherwise, continue with one of the options in Step 4 below.
59
49
 
60
- ## Step 4: Transfer the file to your micro:bit
50
+ ### Step 4: Transfer the file to your micro:bit
61
51
 
62
52
  If the file was saved onto your computer, you will need to transfer it to the micro:bit.
63
53
 
64
- ## Manual transfer
54
+ #### Manual transfer
65
55
 
66
56
  Your `.hex` file (created in Step 3 above) appears as a download at the bottom of the browser.
67
57
  Click on the arrow next to the name of the file and then click **Show in folder**.
@@ -74,7 +64,7 @@ Alternatively, right-click on the hex file, choose **Send to**, and then **MICRO
74
64
 
75
65
  ![](/static/mb/device/usb-windows-sendto.jpg)
76
66
 
77
- ## Step 5: After transferring the file
67
+ ### Step 5: After transferring the file
78
68
 
79
69
  * The LED on the back of your micro:bit flashes during the transfer (which
80
70
  should only take a few seconds).
@@ -1,26 +1,24 @@
1
- # Uploading from Microsoft Edge on Windows
1
+ # Transferring from Microsoft Edge on Windows
2
2
 
3
- How to compile, transfer, and run a program on your micro:bit on **Microsoft Edge**.
3
+ How to compile, transfer, and run a program on your micro:bit with **Microsoft Edge**.
4
4
 
5
5
  While you're writing and testing your programs, you'll mostly be [running them
6
6
  in the simulator](/device/simulator), but once you've finished your program you
7
7
  can **compile** it and run it on your micro:bit.
8
8
 
9
- The basic steps are:
9
+ ## Transfer using a WebUSB connection
10
10
 
11
- 1. Connect your @boardname@ to your computer via USB
12
- 2. Click **Download** to download the `.hex` file
13
- 3. Click the **Save As** button in the bottom bar and save the `.hex` file into the MICROBIT drive
11
+ With Microsoft Edge (version 79 and newer), you can transfer your program to the @boardname@ with a single click. If your browser supports WebUSB, you can use the **one-click download** feature to send your programs to the @boardname@. See the [WebUSB](/device/usb/webusb) page to learn how to pair your @boardname@ with a computer and transfer your programs with a single click.
14
12
 
15
- ## Requirements
13
+ ## Downloading your program as file
16
14
 
17
- You need the following things to transfer and run a script on your micro:bit:
15
+ The basic steps are:
18
16
 
19
- * A-Male to Micro USB cable to connect your computer to your micro:bit. This is
20
- the same cable that is commonly used to connect a smart phone to a computer.
21
- * A PC running Windows 7 or later.
17
+ 1. Connect your @boardname@ to your computer with a USB cable (use an A-Male to Micro USB cable)
18
+ 2. Click **Download** to download the `.hex` file
19
+ 3. Click the **Save As** button in the bottom bar and save the `.hex` file into the MICROBIT drive
22
20
 
23
- ## Step 1: Connect your micro:bit to your computer
21
+ ### Step 1: Connect your micro:bit to your computer
24
22
 
25
23
  First, connect the micro:bit:
26
24
 
@@ -34,7 +32,7 @@ it appears as a new drive under Devices.
34
32
 
35
33
  ![](/static/mb/device/usb-windows-device.jpg)
36
34
 
37
- ## Step 2: Download your program
35
+ ### Step 2: Download your program
38
36
 
39
37
  1. Open your project on @homeurl@
40
38
  2. Click **Download**
@@ -1,10 +1,16 @@
1
- # Uploading programs to your @boardname@
1
+ # Transferring programs to your @boardname@
2
2
 
3
- Most of the time you'll be writing and testing your programs in the [simulator](/device/simulator). Once you've finished your program though, you can **compile** it and run it on your @boardname@. Transferring your program to the @boardname@ is as simple as saving a file to a drive on your computer.
3
+ Most of the time you'll be writing and testing your programs in the [simulator](/device/simulator). Once you've finished your program though, you can **compile** it and run it on your @boardname@. Transferring your program to the @boardname@ is as simple as clicking the **Download** button, or by saving a file to a drive on your computer.
4
4
 
5
- When you plug your @boardname@ into USB, a new drive is created with the **@drivename@** label. This is where you'll save your program.
5
+ ![micro:bit connected using USB](/static/mb/device/usb-thin.jpg)
6
6
 
7
- ![](/static/mb/device/usb-thin.jpg)
7
+ ## Transfer using a WebUSB connection
8
+
9
+ With some newer browsers, you can transfer your program to the @boardname@ with a single click. If your browser supports WebUSB, you can use the **one-click download** feature to send your programs to the @boardname@. See the [WebUSB](/device/usb/webusb) page to learn how to pair your @boardname@ with a computer and transfer your programs with a single click.
10
+
11
+ ## Downloading your program as file
12
+
13
+ If your browser doesn't support WebUSB or you want to use your computer's file system to transfer your program instead, you can download it to the @boardname@ as a file. When you plug your @boardname@ into USB, a new drive is created with the **@drivename@** label. This is where you'll save your program.
8
14
 
9
15
  The basic steps are:
10
16
 
package/docs/device.md CHANGED
@@ -1,16 +1,24 @@
1
1
  # Device
2
2
 
3
+ ### ~ hint
3
4
 
4
- ## ~ hint
5
+ #### Looking to buy a micro:bit?
5
6
 
6
- **Looking to buy a micro:bit?** See the [list of resellers](https://microbit.org/resellers).
7
+ See the [list of resellers](https://microbit.org/resellers).
7
8
 
8
- ## ~
9
+ ### ~
9
10
 
10
11
  All the bits and pieces that make up the BBC micro:bit
11
12
 
12
- ![micro:bit board layout](/static/mb/device-0.png)
13
+ ![micro:bit board layout](/static/mb/device-v2.jpg)
13
14
 
15
+ ### ~ hint
16
+
17
+ #### The current version of micro:bit is v2
18
+
19
+ The version of @boardname@ is now currently at **v2**. See the what's new in MakeCode for programming the [@boardname@ v2](/device/v2).
20
+
21
+ ### ~
14
22
 
15
23
  ## LED Screen and Status LED
16
24
 
@@ -27,17 +35,21 @@ https://www.youtube.com/watch?v=qqBmvHD5bCw
27
35
 
28
36
  ## Buttons
29
37
 
30
- Buttons A and B are a form of input. When you press a button, it completes an electrical circuit.
38
+ Buttons **A** and **B** are a form of input. When you press a button, it completes an electrical circuit.
31
39
  The micro:bit can detect either of its two buttons being pressed/released and be programmed
32
40
  to act on these events.
33
41
 
34
- Button R on the back of the micro:bit is a system button. It has different uses.
35
- When you have downloaded and run your code onto your micro:bit, press Button R to restart and run your program from the beginning.
42
+ Button **R** on the back of the micro:bit is a system button. It has different uses.
43
+ When you have downloaded and run your code onto your micro:bit, press Button **R** to restart and run your program from the beginning.
36
44
 
37
45
  Find out how buttons provide input to the @boardname@ in this video:
38
46
 
39
47
  https://www.youtube.com/watch?v=t_Qujjd_38o
40
48
 
49
+ ## Touch
50
+
51
+ Pins **0**, **1**, **2**, and the board **logo** can work as touch buttons when they are programmed for input.
52
+
41
53
  ## USB connection
42
54
 
43
55
  When you plug in your micro:bit via [USB](/device/usb), it should appear as a ``MICROBIT`` drive.
@@ -47,9 +59,9 @@ the micro:bit will appear as a ``MAINTENANCE`` drive instead of ``MICROBIT``. Th
47
59
 
48
60
  To continue programming your micro:bit YOU MUST unplug your USB and reconnect it. Check that the drive now shows as ``MICROBIT``.
49
61
 
50
- ## ~ hint
62
+ ### ~ hint
51
63
 
52
- ### Open the version file
64
+ #### Open the version file
53
65
 
54
66
  Use with caution!
55
67
  If you click on the drive while it shows the ``MAINTENANCE`` label,
@@ -57,7 +69,7 @@ you can see which version of firmware you have running on your micro:bit.
57
69
  Firmware on your micro:bit should be up-to-date already.
58
70
  You can find the version of firmware in the 'version.txt' file on the micro:bit. See the @boardname@ **[firmware](https://microbit.org/guide/firmware/)** page for more about checking your board's firmware version.
59
71
 
60
- ## ~
72
+ ### ~
61
73
 
62
74
  ## Compass
63
75
 
@@ -79,7 +91,11 @@ https://www.youtube.com/watch?v=byngcwjO51U
79
91
  ## Pins
80
92
 
81
93
  The [pins](/device/pins) can be a form of electrical input or output.
82
- There are labels for the input/output pins ``P0``, ``P1``, ``P2``, which you can attach external sensors to such as thermometers or moisture detectors.
94
+ There are labels for the input/output pins **0**, **1**, **2**, which you can attach external sensors to such as thermometers or moisture detectors.
95
+
96
+ ## Microphone
97
+
98
+ Using the microphone, your programs can detect sounds that are present. You can check for loud or quiet sounds and find out what their sound level is.
83
99
 
84
100
  ## Light level
85
101
 
@@ -119,7 +135,7 @@ and [click here to read more about the error messages you might get](/device/err
119
135
  When your micro:bit is connected to your computer with the micro USB, it doesn’t need another power source.
120
136
  When your micro:bit isn’t connected to your computer, tablet or mobile, you will need 2 x AAA 1.5 V batteries to power it.
121
137
 
122
- The pins labelled 3V and GND are the power supply pins.
138
+ The pins labelled **3V** and **GND** are the power supply pins.
123
139
  You can attach an external device such as a motor to these and power it using the battery or USB.
124
140
 
125
141
  ## Serial Communication
package/docs/docs.md CHANGED
@@ -21,7 +21,7 @@
21
21
 
22
22
  ## More questions?
23
23
 
24
- * [Frequently Asked Question](/faq)
24
+ * [Frequently Asked Questions](/faq)
25
25
  * [Help Translate](/translate)
26
26
  * [Embedding project](/share)
27
27
 
@@ -55,6 +55,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
55
55
  "name": "Wearables",
56
56
  "url": "/extensions#wearables",
57
57
  "cardType": "link"
58
+ }, {
59
+ "name": "Utilities",
60
+ "url": "/extensions#utilities",
61
+ "cardType": "link"
58
62
  }]
59
63
  ```
60
64
 
@@ -172,6 +176,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
172
176
 
173
177
  ```codecard
174
178
  [{
179
+ "name": "SGBotic Ultimate SR04",
180
+ "url":"/pkg/SGBotic/pxt-SGBotic-Ultimate-SR04-RGB",
181
+ "cardType": "package"
182
+ }, {
175
183
  "name": "TCS3200 Color sensor",
176
184
  "url":"/pkg/joy-it/pxt-SEN-Color",
177
185
  "cardType": "package"
@@ -302,6 +310,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
302
310
 
303
311
  ```codecard
304
312
  [{
313
+ "name": "iClass IoT",
314
+ "url":"/pkg/KelieLeung/pxt-iClassIoT",
315
+ "cardType": "package"
316
+ }, {
305
317
  "name": "Kittenbot Wifi",
306
318
  "url":"/pkg/KittenBot/pxt-kittenwifi",
307
319
  "cardType": "package"
@@ -344,6 +356,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
344
356
 
345
357
  ```codecard
346
358
  [{
359
+ "name": "HacKids hack:bit",
360
+ "url": "/pkg/HackidsEdu/pxt-hackbit",
361
+ "cardType": "package"
362
+ }, {
347
363
  "name": "KittenBot Sugar",
348
364
  "url": "/pkg/KittenBot/pxt-sugar",
349
365
  "cardType": "package"
@@ -376,8 +392,12 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
376
392
  "url":"/pkg/elecfreaks/pxt-PlanetX",
377
393
  "cardType": "package"
378
394
  }, {
379
- "name": "Inksmith Climate Action Kit",
380
- "url":"/pkg/dugbraden/pxt-climate-action-kit",
395
+ "name": "Inksmith Climate Action Kit: Land",
396
+ "url":"/pkg/climate-action-kits/pxt-climate-action-kit-land",
397
+ "cardType": "package"
398
+ }, {
399
+ "name": "Inksmith Climate Action Kit: Energy",
400
+ "url":"/pkg/climate-action-kits/pxt-climate-action-kit-land",
381
401
  "cardType": "package"
382
402
  }, {
383
403
  "name": "Grove inventor kit",
@@ -453,6 +473,14 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
453
473
 
454
474
  ```codecard
455
475
  [{
476
+ "name": "Kittenbot miniLFR",
477
+ "url":"/pkg/KittenBot/pxt-minilfr",
478
+ "cardType": "package"
479
+ }, {
480
+ "name": "Cytron ZOOM:BIT",
481
+ "url":"/pkg/CytronTechnologies/pxt-zoombit",
482
+ "cardType": "package"
483
+ }, {
456
484
  "name": "Kid Spark Spark:bit",
457
485
  "url":"/pkg/KidSpark/pxt-sparkbit",
458
486
  "cardType": "package"
@@ -687,6 +715,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
687
715
 
688
716
  ```codecard
689
717
  [{
718
+ "name": "PT-BOT KidsBIT",
719
+ "url":"/pkg/iBuilds/pxt-PTKidsBIT-IoT",
720
+ "cardType": "package"
721
+ }, {
690
722
  "name": "Kitronik Air Quality & Environmental Board",
691
723
  "url":"/pkg/KitronikLtd/pxt-kitronik-air-quality",
692
724
  "cardType": "package"
@@ -808,6 +840,14 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
808
840
  ## Utilities
809
841
  ```codecard
810
842
  [{
843
+ "name": "Lego PF trasmitter",
844
+ "url":"/pkg/aorczyk/lego-pf-transmitter",
845
+ "cardType": "package"
846
+ }, {
847
+ "name": "Kodely dot",
848
+ "url":"/pkg/Kodely-io/dot",
849
+ "cardType": "package"
850
+ }, {
811
851
  "name": "Wait until...",
812
852
  "url":"/pkg/TeacherPinky/Wait-Until-Blocks",
813
853
  "cardType": "package"
@@ -256,10 +256,10 @@ Remember to turn your sound on!
256
256
 
257
257
  ---
258
258
 
259
- ► Touch the gold logo at the top of your @boardname@ (it looks like a pig snout 🐽) on the simulator. You'll notice that a second @boardname@ appears.
259
+ ► Touch the gold **micro:bit logo** at the top of your @boardname@ on the simulator. You'll notice that a second @boardname@ appears.
260
260
  💡 If your screen is too small, you might not be able to see it.
261
261
 
262
- ► Touch the 🐽 again to send messages to Sky 🐖
262
+ ► Touch the logo again to send messages to Sky 🐖
263
263
  **Press** to send a dot.
264
264
  **Long press** (count to 3!) to send a dash.
265
265
 
@@ -146,7 +146,7 @@ Check out the simulator and make sure your speakers are on 🔊
146
146
 
147
147
  Play with Cyrus to see how they react 🐹
148
148
  **Click on the SHAKE button** to shake Cyrus.
149
- **Touch the gold logo at the top** (it looks like a piggy snout 🐽) to tickle Cyrus.
149
+ **Touch the gold logo at the top** to tickle Cyrus.
150
150
 
151
151
  If you have a new @boardname@ (the one with the **shiny gold** logo at the top), download this code and try it out!
152
152
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pxt-microbit",
3
- "version": "4.1.7",
3
+ "version": "4.1.8",
4
4
  "description": "micro:bit target for Microsoft MakeCode (PXT)",
5
5
  "keywords": [
6
6
  "JavaScript",
package/targetconfig.json CHANGED
@@ -159,7 +159,7 @@
159
159
  "BrightWearables/pxt-microbit-brightboard",
160
160
  "EBOTICS/pxt-eboticsMIBO",
161
161
  "KitronikLtd/pxt-kitronik-halohd",
162
- "dugbraden/pxt-climate-action-kit",
162
+ "climate-action-kits/pxt-climate-action-kit-land",
163
163
  "alsrobot-microbit-makecode-packages/MiniCruise",
164
164
  "4tronix/ServoBit",
165
165
  "DFRobot/pxt-maqueen",
@@ -228,9 +228,19 @@
228
228
  "KidSpark/pxt-sparkbit",
229
229
  "BPI-STEAM/pxt-triodecar",
230
230
  "KitronikLtd/pxt-kitronik-air-quality",
231
+ "KitronikLtd/pxt-kitronik-air-quality-v2-only",
231
232
  "artec-kk/pxt-artecrobo-kit",
232
233
  "TeacherPinky/Wait-Until-Blocks",
233
- "KittenBot/pxt-kittenwifi"
234
+ "KittenBot/pxt-kittenwifi",
235
+ "SGBotic/pxt-SGBotic-Ultimate-SR04-RGB",
236
+ "CytronTechnologies/pxt-zoombit",
237
+ "Kodely-io/dot",
238
+ "climate-action-kits/pxt-climate-action-kit-energy",
239
+ "HackidsEdu/pxt-hackbit",
240
+ "aorczyk/lego-pf-transmitter",
241
+ "KittenBot/pxt-minilfr",
242
+ "iBuilds/pxt-PTKidsBIT-IoT",
243
+ "KelieLeung/pxt-iClassIoT"
234
244
  ],
235
245
  "preferredRepos": [
236
246
  "Microsoft/pxt-neopixel",
@@ -279,7 +289,7 @@
279
289
  "sparkfun/pxt-gator-particle": "dv:mbcodal",
280
290
  "sparkfun/pxt-gator-microphone": "dv:mbcodal",
281
291
  "rebeccaclavier/pxt-bmp280": "dv:mbcodal",
282
- "mu-opensource/pxt-muvision": "min:v1.2.21",
292
+ "mu-opensource/pxt-muvision": "min:v1.2.25",
283
293
  "elecfreaks/pxt-PlanetX": "min:v0.13.1",
284
294
  "bsiever/microbit-pxt-timeanddate": "min:v2.0.11"
285
295
  },