pxt-microbit 8.1.6 → 8.1.9

package/docs/device/serial.md

@@ -26,16 +26,19 @@ Unfortunately, using the serial library requires quite a bit of a setup.
 
 ### ~ hint
 
-**Windows earlier than 10**
+#### Windows earlier than 10
 
 If you are running a Windows version earlier than 10, you must [install a device driver](https://os.mbed.com/docs/latest/tutorials/windows-serial-driver.html) (for the computer to recognize the serial interface of the micro:bit).
 
-## ~
+### ~
+
 Also, if you don't see the serial port as one of your computer's devices, you might need to [update the firmware](/device/firmware) on the @boardname@. Find the device name for the attached serial port in the following instructions for your operating system.
 
-### Windows > Tera Term
+## Windows
+
+### Tera Term
 
-* Install the terminal emulator [Tera Term](https://ttssh2.osdn.jp/index.html.en). At the time of this writing, the latest version is 4.88 and can be downloaded [from here](http://en.osdn.jp/frs/redir.php?m=jaist&f=%2Fttssh2%2F63767%2Fteraterm-4.88.exe). Follow the instructions from the installer.
+* Install the terminal emulator [Tera Term](https://teratermproject.github.io/index-en.html). The the latest release and can be downloaded [from here](https://github.com/TeraTermProject/teraterm/releases). Scroll down to the "Assets" section and download the release package that is appropriate for your computer. For example, if you have an x64 based processor, click on the one that ends in "x64.exe".
 
 Once both the driver and the terminal emulator are installed, plug in the micro:bit and wait until the device is fully setup. Then, open TeraTerm.
 
@@ -47,7 +50,7 @@ You should be good. Feel free to hit `Setup` > `Save Setup` in the menus to eras
 
 Please note that Windows will assign you a different COM port if you plug in another micro:bit. If you're juggling between micro:bits, you'll have to change the COM port every time.
 
-### Windows > Putty
+### Putty
 
 If you prefer another terminal emulator (such as [PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/)), here are some instructions.
 

package/docs/device/v2.md

@@ -9,7 +9,7 @@ Let's learn how this works in MakeCode...
 ![works with micro:bit v2 only image](/static/v2/v2-only.png)
 <br/>
 
-The following blocks require the micro:bit v2 hardware to run.
+Here are the standard blocks that **require** micro:bit v2 hardware to run.
 
 ```block
 let pressed = input.logoIsPressed()
@@ -23,7 +23,7 @@ input.onSound(DetectedSound.Loud, function () {})
 input.onLogoEvent(TouchButtonEvent.Pressed, function () {})
 ```
 
-If your program tries to run any of these blocks on a micro:bit v1 board, you will see the ``927`` error code scroll across your screen.
+If your program tries to run any of these blocks on a micro:bit **v1** board, you will see the **927** error code scroll across your screen.
 
 ```sim
 basic.forever(function() {
@@ -32,6 +32,15 @@ basic.forever(function() {
 })
 ```
 
+### ~ alert
+
+#### v2 features in extension blocks
+
+if you're using blocks from a loaded extension, such as [Datalogger](/reference/datalogger), that are using any newer **v2** features on a **v1** board, you will also see the **927** error when your program tries to run those blocks.
+
+### ~
+
+
 ### New blocks reference
 
 The reference information for the new blocks introduced for micro:bit v2:

package/docs/extensions/extension-gallery.md

@@ -70,6 +70,10 @@ Many extensions are available to work with interface kits, add-on hardware, or o
 
 ```codecard
 [{
+    "name": "TM1638",
+    "url": "/pkg/NathanPervin/pxt-tm1638",
+    "cardType": "package"
+}, {
     "name": "Pythom1234 OLED Display SSD1306 128x64",
     "url": "/pkg/Pythom1234/pxt-oled",
     "cardType": "package"
@@ -388,6 +392,10 @@ Many extensions are available to work with interface kits, add-on hardware, or o
 
 ```codecard
 [{
+   "name": "FWD Edu Coding For Good Kit",
+   "url": "/pkg/Forward-Education/pxt-coding-for-good",
+   "cardType": "package"
+}, {
    "name": "Smarthon Smart Home IoT Maker Kit",
    "url": "/pkg/SMARTHON/pxt-smarthome",
    "cardType": "package"
@@ -555,6 +563,10 @@ Many extensions are available to work with interface kits, add-on hardware, or o
   "name": "DFRobot HuskyLens",
   "url":"/pkg/DFRobot/pxt-DFRobot_HuskyLens",
   "cardType": "package"
+}, {
+  "name": "DFRobot HuskyLens 2",
+  "url":"/pkg/DFRobot/pxt-DFRobot_HuskyLensV2",
+  "cardType": "package"
 }]
 ```
 ## Robotics
@@ -911,6 +923,10 @@ Many extensions are available to work with interface kits, add-on hardware, or o
 
 ```codecard
 [{
+    "name": "BestModules BMduino",
+    "url": "/pkg/BestModules-Libraries/pxt-bmduino",
+    "cardType": "package"
+}, {
     "name": "Backyard Brains Spiker:Bit",
     "url": "/pkg/BackyardBrains/pxt-spikerbit",
     "cardType": "package"

package/docs/projects/spy/tug-of-led.md

@@ -20,7 +20,7 @@ let rope = 2
 
 ## {Step 2}
 
-Add a ``||basic:forever||`` loop that turns on the LED at the position set in ``||variables:rope||``.
+Add a ``||basic:forever||`` loop that will ``||basic:clear screen||`` and turn on the LED at the position set in ``||variables:rope||``.
 
 ```spy
 let rope = 2

package/docs/projects/tug-of-led.md

@@ -19,7 +19,7 @@ let rope = 2
 
 ## {Step 2}
 
-Add a ``||basic:forever||`` loop that turns on the LED at the ``||variables:rope||`` position.
+In the ``||basic:forever||`` loop, put in a ``||basic:clear screen||`` and plot an LED at the ``||variables:rope||`` position.
 
 ```blocks
 let rope = 2

package/docs/projects/turtle-square.md

@@ -43,7 +43,7 @@ input.onButtonPressed(Button.A, function() {
 
 ## "for" is for repetition
 
-Did you notice the pattern of repeated blocks needed to draw a square? Try using a ``for`` loop to achieve the same effect.
+Did you notice the pattern of repeated blocks needed to draw a square? Try using a ``for`` loop with an `index` limit of **3** to achieve the same effect.
 
 ```blocks
 input.onButtonPressed(Button.A, function() {

package/docs/reference/radio/on-received-message.md

@@ -2,7 +2,7 @@
 
 ## Example #example
 
-Send a ``Hello`` message when button ``A`` is pressed, ``Goodbye`` when button ``B`` is pressed. If the messages are received, display either a ``heart`` or a ``scissor`` for the messages.
+Send a ``Hello`` message when button ``A`` is pressed, ``Goodbye`` when button ``B`` is pressed. If the messages are received, display either a ``heart`` for the ``Hello`` message or a ``scissor`` for the ``Goodbye`` message.
 
 ```blocks
 enum RadioMessage {
@@ -10,6 +10,7 @@ enum RadioMessage {
     Hello = 49337,
     Goodbye = 16885
 }
+radio.setGroup(3)
 input.onButtonPressed(Button.A, function () {
     radio.sendMessage(RadioMessage.Hello)
 })

package/docs/reference/radio/send-message.md

@@ -2,7 +2,7 @@
 
 ## Example #example
 
-Send a ``Hello`` message when button ``A`` is pressed, ``Goodbye`` when button ``B`` is pressed. If the messages are received, display either a ``heart`` or a ``scissor`` for the messages.
+Send a ``Hello`` message when button ``A`` is pressed, ``Goodbye`` when button ``B`` is pressed. If the messages are received, display either a ``heart`` for the ``Hello`` message or a ``scissor`` for the ``Goodbye`` message.
 
 ```blocks
 enum RadioMessage {
@@ -10,6 +10,7 @@ enum RadioMessage {
     Hello = 49337,
     Goodbye = 16885
 }
+radio.setGroup(3)
 input.onButtonPressed(Button.A, function () {
     radio.sendMessage(RadioMessage.Hello)
 })

package/docs/reference/serial/on-data-received.md

@@ -1,8 +1,7 @@
-# Serial On Data Received
+# on Data Received
 
 Registers an event to be fired when one of the delimiter is matched.
 
-
 ```sig
 serial.onDataReceived(",", function() {})
 ```
@@ -13,10 +12,10 @@ serial.onDataReceived(",", function() {})
 
 ## Example
 
-Read values separated by `,`:
+Read values separated by a comma `,`.
 
 ```blocks
-serial.onDataReceived(serial.delimiters(Delimiters.Comma), () => {
+serial.onDataReceived(serial.delimiters(Delimiters.Comma), function() {
     basic.showString(serial.readUntil(serial.delimiters(Delimiters.Comma)))
 })
 ```
@@ -24,6 +23,5 @@ serial.onDataReceived(serial.delimiters(Delimiters.Comma), () => {
 ## See also
 
 [serial](/device/serial),
-[serial write line](/reference/serial/write-line),
-[serial write value](/reference/serial/write-value)
-
+[write line](/reference/serial/write-line),
+[write value](/reference/serial/write-value)

package/docs/reference/serial/read-buffer.md

@@ -34,7 +34,7 @@ Read character data from the serial port one row at a time. Write the rows to an
 serial.setRxBufferSize(10)
 for (let i = 0; i < 24; i++) {
     let rowData = serial.readBuffer(10)
-    pins.i2cWriteBuffer(65, rowData, false);
+    pins.i2cWriteBuffer(65, rowData, false)
 }
 ```
 

package/docs/reference/serial/read-line.md

@@ -1,4 +1,4 @@
-# Serial Read Line
+# read Line
 
 Read a line of text from the serial port.
 
@@ -14,7 +14,6 @@ This function expects the line it reads to be terminated with the `\n`
 character. If your terminal software does not terminate lines with
 `\n`, this function will probably never return a value.
 
-
 You can override the ``serial.NEW_LINE_DELIMITER`` field to change the newline delimiter.
 
 ### ~
@@ -30,7 +29,7 @@ The following example requests the user's name, then repeats it to greet the use
 ```blocks
 basic.forever(() => {
     serial.writeLine("What is your name?")
-    let answer = serial.readLine();
+    let answer = serial.readLine()
     serial.writeString("Hello,")
     serial.writeLine(answer)
 })
@@ -39,5 +38,5 @@ basic.forever(() => {
 ## See also
 
 [serial](/device/serial),
-[serial write line](/reference/serial/write-line),
-[serial write value](/reference/serial/write-value)
+[write line](/reference/serial/write-line),
+[write value](/reference/serial/write-value)

package/docs/reference/serial/read-string.md

@@ -1,4 +1,4 @@
-# Serial Read String
+# read String
 
 Read the buffered serial data as a string.
 
@@ -23,5 +23,5 @@ basic.forever(function() {
 ## See also
 
 [serial](/device/serial),
-[serial write line](/reference/serial/write-line),
-[serial write value](/reference/serial/write-value)
+[write line](/reference/serial/write-line),
+[write value](/reference/serial/write-value)

package/docs/reference/serial/read-until.md

@@ -1,4 +1,4 @@
-# Serial Read Until
+# read Until
 
 Read a text from the serial port until a delimiter is found.
 
@@ -24,5 +24,5 @@ basic.forever(() => {
 ## See also
 
 [serial](/device/serial),
-[serial write line](/reference/serial/write-line),
-[serial write value](/reference/serial/write-value)
+[write line](/reference/serial/write-line),
+[write value](/reference/serial/write-value)

package/docs/reference/serial/set-rx-buffer-size.md

@@ -8,7 +8,7 @@ serial.setRxBufferSize(10)
 
 ## Parameters
 
-* **size**: desired length of the reception buffer
+* **size**: desired length of the reception buffer (maximum 254)
 
 ## Example
 

package/docs/reference/serial/set-tx-buffer-size.md

@@ -8,7 +8,7 @@ serial.setTxBufferSize(10)
 
 ## Parameters
 
-* **size**: desired length of the transmission buffer
+* **size**: desired length of the transmission buffer (maximum 254)
 
 ## Example
 

package/docs/reference/serial/write-line.md

@@ -1,4 +1,4 @@
-# Serial Write Line
+# write Line
 
 Write a string to the [serial](/device/serial) port and start a new line of text 
 by writing `\r\n`.
@@ -57,6 +57,6 @@ basic.forever(function() {
 ## See also
 
 [serial](/device/serial),
-[serial write number](/reference/serial/write-number),
-[serial write string](/reference/serial/write-string),
-[serial write value](/reference/serial/write-value)
+[write number](/reference/serial/write-number),
+[write string](/reference/serial/write-string),
+[write value](/reference/serial/write-value)

package/docs/reference/serial/write-number.md

@@ -1,4 +1,4 @@
-# Serial Write Number
+# write Number
 
 Write a number to the [serial](/device/serial) port.
 
@@ -6,22 +6,53 @@ Write a number to the [serial](/device/serial) port.
 serial.writeNumber(0)
 ```
 
+A number value is written to the serial port as characters in a string representation. The number `876`, for example:
+
+```block
+serial.writeNumber(876)
+```
+
+The receiving serial port will see this number as the 3 characters:
+
+```
+876
+```
+
 ## Parameters
 
 * `value` is the [number](/types/number) to write to the serial port
 
-## Example: one two three
+### ~ reminder
+
+#### Simulator data log
+
+When a number is written to the serial port, it's sent immediately over the serial connection. However, when you code with  ``||serial:write number||`` in the Editor, the simulator's data log may not display the output data right away. The characters that represent the number may get queued in the data log buffer and won't display until:
 
-This program repeatedly writes a 3-digit number to the serial port.
+* a 'newline' line character is received (`\n`)
+
+-- or --
+
+* log data buffer limit is reached (currently set at `255` characters).
+
+If you want to see the string displayed immediately, use a ``||serial:write line||`` with an empty string right after the ``||serial:write number||``.
+
+### ~
+
+## Examples
+
+### One, Two, Three
+
+This program repeatedly writes a 3-digit number as a line to the serial port.
 
 ```blocks
 basic.forever(function() {
     serial.writeNumber(123)
+    serial.writeLine("")
     basic.pause(5000)
 });
 ```
 
-## Example: plot bar graph does serial
+### Plot bar graph does serial
 
 If you use the ``led.plotBarGraph`` function, it writes the number
 being plotted to the serial port too.
@@ -36,7 +67,6 @@ basic.forever(function() {
 ## See also
 
 [serial](/device/serial),
-[serial write line](/reference/serial/write-line),
-[serial write value](/reference/serial/write-value),
-[serial write numbers](/reference/serial/write-numbers)
-
+[write line](/reference/serial/write-line),
+[write value](/reference/serial/write-value),
+[write numbers](/reference/serial/write-numbers)

package/docs/reference/serial/write-numbers.md

@@ -1,4 +1,4 @@
-# Serial Write Numbers
+# write Numbers
 
 Write an array of numbers to the [serial](/device/serial) port.
 
@@ -41,5 +41,5 @@ basic.forever(function() {
 ## See also
 
 [serial](/device/serial),
-[serial write line](/reference/serial/write-line),
-[serial write value](/reference/serial/write-value)
+[write line](/reference/serial/write-line),
+[write value](/reference/serial/write-value)

package/docs/reference/serial/write-string.md

@@ -1,4 +1,4 @@
-# Serial Write String
+# write String
 
 Write a string to the [serial](/device/serial) port,
 without starting a new line afterward.
@@ -7,6 +7,22 @@ without starting a new line afterward.
 serial.writeString("")
 ```
 
+### ~ reminder
+
+#### Simulator data log
+
+When a string is written to the serial port, it's sent immediately over the serial connection. However, when you code with  ``||serial:write string||`` in the Editor, the simulator's data log may not display the output data right away. The characters that represent the string may get queued in the data log buffer and won't display until:
+
+* a 'newline' line character is received (`\n`)
+
+-- or --
+
+* log data buffer limit is reached (currently set at `255` characters).
+
+If you want to see the string displayed immediately, use a ``||serial:write line||`` with an empty string right after the ``||serial:write string||``.
+
+### ~
+
 ## Parameters
 
 * `text` is the [string](/types/string) to write to the serial port
@@ -26,6 +42,6 @@ basic.forever(function() {
 ## See also
 
 [serial](/device/serial),
-[serial write line](/reference/serial/write-line),
-[serial write number](/reference/serial/write-number),
-[serial write value](/reference/serial/write-value)
+[write line](/reference/serial/write-line),
+[write number](/reference/serial/write-number),
+[write value](/reference/serial/write-value)

package/docs/reference/serial/write-value.md

@@ -40,8 +40,10 @@ basic.forever(function() {
 
 ### ~hint
 
+#### Radio-Serial gateway
+
 The [send value](/reference/radio/send-value) function broadcasts
-string/number pairs.  You can use a second @boardname@ to receive them,
+string/number pairs. You can use a second @boardname@ to receive them,
 and then send them directly to the serial port with ``write value``.
 
 ### ~
@@ -49,6 +51,6 @@ and then send them directly to the serial port with ``write value``.
 ## See also
 
 [serial](/device/serial),
-[serial write line](/reference/serial/write-line),
-[serial write number](/reference/serial/write-number),
+[write line](/reference/serial/write-line),
+[write number](/reference/serial/write-number),
 [send value](/reference/radio/send-value)

package/docs/translate.md

@@ -6,13 +6,13 @@
 
 #### Help translate
 
-Looking to help translate the site for **[microbit.org](http://microbit.org)**? Try http://translate.microbit.org/ to help the Microbit Foundation!
+Looking to help translate the site for **[microbit.org](http://microbit.org)**? Try http://translate.microbit.org/ to help the Micro:bit Foundation!
  
 ### ~
 
 ## #target-files
 
-When you select your language from the [MakeCode](https://crowdin.com/project/makecode) project home page, you'll find all of the localization files for MakeCode shown in a folder tree. The strings to translate for the @boardname@ are found in the files under the **microbit** folder for the current language.
+When you select your language from the [MakeCode](https://crowdin.com/project/makecode) project homepage, you'll find all of the localization files for MakeCode shown in a folder tree. The strings to translate for the @boardname@ are found in the files under the **microbit** folder for the current language.
 
 ![microbit strings files](/static/mb/translate/crowdin-folder.png)
 
@@ -22,34 +22,34 @@ The files listed in the following sections provide a guide to how each of the tr
 
 ### Editor
 
-There a a few files that are specific to the MakeCode editor itself. These contain strings for the editor UI and the simulator. They are essential to translate and should be prioritized before the other files.
+There are a few files that are specific to the MakeCode editor itself. These contain strings for the editor UI and the simulator. They are essential to translate and should be prioritized before the other files.
 
 | File | Description |
 | - | - |
-| strings.json | Common strings that shared by all MakeCode editors. **Note**: This file is located at the MakeCode project's root folder rather than under **microbit** |
+| strings.json | Common strings that are shared by all MakeCode editors. **Note**: This file is located at the MakeCode project's root folder rather than under **microbit** |
 | target-strings.json | Strings custom to the @boardname@ editor interface |
 | sim-strings.json | Strings for the @boardname@ simulator |
 <br/>
 
-This is an example of the editor with it's interface elements localized:
+This is an example of the editor with its interface elements localized:
 
 ![Translated editor elements](/static/mb/translate/target-strings.jpg)
 
 ### Blocks
 
-The strings for the programming code blocks all have names in the form of '_name_-strings.json' and '_name_-jsdoc-strings.json'. The _name_ part of the filename often refers to which set of blocks or the extension tht the blocks come from. 
+The strings for the programming code blocks all have names in the form of '_name_-strings.json' and '_name_-jsdoc-strings.json'. The _name_ part of the filename often refers to which set of blocks or the extension that the blocks come from.
 
 | File | Description |
 | - | - |
-| core-jsdoc-strings.json |  Description text for code elements of the [basic](/reference/basic) and core [blocks](/blocks). **Note**: this file contains strings for the fundamental set of coding blocks and should be prioritized over the other strings files for blocks |
+| core-jsdoc-strings.json | Description text for code elements of the [basic](/reference/basic) and core [blocks](/blocks). **Note**: this file contains strings for the fundamental set of coding blocks and should be prioritized over the other strings files for blocks |
 | core-strings.json | Display text for the [basic](/reference/basic) and core [blocks](/reference/blocks). **Note**: this file contains strings for the fundamental set of coding blocks and should be prioritized over the other strings files for blocks |
 | radio-jsdoc-strings.json | Description text for code elements of the [radio](/reference/radio) blocks |
 | radio-strings.json | Display text for the [radio](/reference/radio) blocks |
-| radio-broadcast-jsdoc-strings.json |  Description text for code elements of the radio broadcast blocks |
+| radio-broadcast-jsdoc-strings.json | Description text for code elements of the radio broadcast blocks |
 | radio-broadcast-strings.json | Display text for the radio broadcast blocks |
 | servo-jsdoc-strings.json | Description text for code elements of the [servo](/reference/servos) blocks |
 | servo-strings.json | Display text for the [servo](/reference/servos) blocks |
-| bluetooth-jsdoc-strings.json | Description text for code elements of the [bluetooth](/reference/bluetooth) blocks
+| bluetooth-jsdoc-strings.json | Description text for code elements of the [bluetooth](/reference/bluetooth) blocks |
 | bluetooth-strings.json | Display text for the [bluetooth](/reference/bluetooth) blocks |
 | devices-jsdoc-strings.json | Description text for code elements of the _connected devices_ blocks |
 | devices-strings.json | Display text for the _connected devices_ blocks |
@@ -57,13 +57,13 @@ The strings for the programming code blocks all have names in the form of '_name
 | flashlog-strings.json | Display text for the _flashlog_ blocks |
 | datalogger-jsdoc-strings.json | Description text for code elements of the [datalogger](/reference/datalogger) blocks |
 | datalogger-strings.json | Display text for the [datalogger](/reference/datalogger) blocks |
-| jacdac-jsdoc-strings.json | Description text for code elements of the _jacdac_ blocks
+| jacdac-jsdoc-strings.json | Description text for code elements of the _jacdac_ blocks |
 | jacdac-strings.json | Display text for the _jacdac_ blocks |
-| color-jsdoc-strings.json | Description text for code elements of the _color_ blocks
+| color-jsdoc-strings.json | Description text for code elements of the _color_ blocks |
 | color-strings.json | Display text for the _color_ blocks |
-| microphone-jsdoc-strings.json | Description text for code elements of the _microphone_ blocks
+| microphone-jsdoc-strings.json | Description text for code elements of the _microphone_ blocks |
 | microphone-strings.json | Display text for the _microphone_ blocks |
-| settings-jsdoc-strings.json | Description text for code elements of the _settings_ blocks
+| settings-jsdoc-strings.json | Description text for code elements of the _settings_ blocks |
 | settings-strings.json | Display text for the _settings_ blocks |
 <br/>
 
@@ -73,7 +73,7 @@ Here are some examples of translated blocks:
 
 ### Document pages
 
-Document pages contain the text for any markdown page available on the MakeCode editor site. These include code block reference, projects, tutorials, how to information, etc.
+Document pages contain the text for any markdown page available on the MakeCode editor site. These include code block reference, projects, tutorials, how-to information, etc.
 
 | File | Description |
 | - | - |

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "pxt-microbit",
-    "version": "8.1.6",
+    "version": "8.1.9",
     "description": "micro:bit target for Microsoft MakeCode (PXT)",
     "keywords": [
         "JavaScript",
@@ -45,8 +45,8 @@
         "typescript": "4.8.3"
     },
     "dependencies": {
-        "pxt-common-packages": "13.1.2",
-        "pxt-core": "12.2.8"
+        "pxt-common-packages": "13.2.3",
+        "pxt-core": "12.3.3"
     },
     "overrides": {}
 }

package/pxtarget.json

@@ -200,7 +200,7 @@
                 "codalTarget": {
                     "name": "codal-microbit-v2",
                     "url": "https://github.com/lancaster-university/codal-microbit-v2",
-                    "branch": "v0.3.4",
+                    "branch": "v0.3.5",
                     "type": "git"
                 },
                 "codalBinary": "MICROBIT",
@@ -519,6 +519,7 @@
             "it",
             "ja",
             "ko",
+            "lo",
             "nl",
             "nb",
             "nn-NO",

package/targetconfig.json

@@ -9,7 +9,7 @@
                 "tags": [ "Lights and Display" ],
                 "simx": {
                     "sha": "0825d56f78528c57af100a96abdfe2162f59945a",
-                    "devUrl": "http://localhost:3000"
+                    "devUrl": "http://microbit-apps.github.io/display-shield/"
                 }
             },
             "microsoft/pxt-microturtle": {
@@ -434,6 +434,10 @@
             "backyardbrains/pxt-spikerbit": { "tags": [ "Science" ] },
             "siyeenove/pxt_mshield": { "tags": [ "Robotics" ] },
             "siyeenove/pxt_pybit": { "tags": [ "Robotics" ] },
+            "nathanpervin/pxt-tm1638": { "tags": [ "Lights and Display" ] },
+            "bestmodules-libraries/pxt-bmduino": { "tags": [ "Science" ] },
+            "forward-education/pxt-coding-for-good": { "tags": [ "Science" ] },
+            "dfrobot/pxt-dfrobot_huskylensv2": { "tags": [ "Science" ] },
             "microsoft/pxt-simx-sample": {
                 "simx": {
                     "sha": "7301f5900879b85127482d79bab48f03c25690a8",