npmpackage.info

Gathering detailed insights and metrics for pxt-maker

Other packages similar to pxt-maker

pxt-common-packages

13.1.0

Microsoft MakeCode (PXT) common packages

Gathering detailed insights and metrics for pxt-maker

pxt-maker - 0.15.66 | npmpackage.info

pxt-maker

MakeCode target for "Maker" boards (beta)

0.15.66

124

NOASSERTION

TypeScript

21.43 MB

5.1

Installations

npm install pxt-maker

Developer Guide

BETA

Typescript

No

Module System

N/A

Node Version

8.17.0

NPM Version

6.13.4 Pull Requests

Open

10

Total

270

Closed

34

Merged

226

Issues

Open

34

Total

98

Closed

64

Releases

Unable to fetch releases

Languages

TypeScript

Less

JavaScript

HTML

Shell

C++

TypeScript (95.86%)

Less (3.18%)

JavaScript (0.55%)

HTML (0.32%)

Shell (0.09%)

C++ (0.01%)

Developer

microsoft

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

NOASSERTION License

124 Stars

1,407 Commits

81 Forks

16 Watchers

27 Branches

53 Contributors

Updated on Jul 10, 2025

Maintainers

View All 53 Contributors

Package Meta Information

Latest Version

0.15.66

Package Id

pxt-maker@0.15.66

Unpacked Size

21.43 MB

Size

4.54 MB

File Count

184

NPM Version

6.13.4

Node Version

8.17.0

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

pxt-common-packages pxt-core webusb

Dev Dependencies

@types/marked @types/node @types/web-bluetooth semantic-ui-less typescript

MakeCode Maker

This is an experimental code editor for maker boards - try it at https://maker.makecode.com.

Read the docs

Who is this for?

This editor is meant for micro-controllers that are friendly to breadboarding. The editor is based on Microsoft MakeCode.

Local Dev Server

The local server lets you to run the editor and serve the documentation from your own computer.

Setup

Install Node.js 8.9.4 or higher.
Install Docker if you are going to edit any .cpp files.
Clone the pxt repository.

git clone https://github.com/microsoft/pxt
cd pxt

Install the dependencies of Microsoft/pxt and build it

npm install
npm run build
cd ..

Clone the Microsoft/pxt-common-packages repository

git clone https://github.com/microsoft/pxt-common-packages
cd pxt-common-packages
npm install
cd ..

Clone the Microsoft/pxt-maker repository

git clone https://github.com/microsoft/pxt-maker
cd pxt-maker

Install the PXT command line (add sudo for Mac/Linux shells).

npm install -g pxt

Install the pxt-maker dependencies.

npm install

Link pxt-maker back to base pxt repo (add sudo for Mac/Linux shells).

rm -Rf node_modules/pxt-core
rm -Rf node_modules/pxt-common-packages
pxt link ../pxt
pxt link ../pxt-common-packages

If you want to know if your folders are link, run ls -l and it will indicate them.

ls -l node_modules/

Note the above command assumes the folder structure of

       maker.makecode.com
          |
  ----------------------------------
  |       |                        |
 pxt      pxt-common-packages  pxt-maker

Refresh dal.d.ts files

Whenever you make changes to the #defines in the .cpp files, you will have to refresh the dal.d.ts files. For that, run

pxt builddaldts

CODAL changes

If you need to do changes to CODAL itself, follow these steps.

create a new project in the web editor, then close the web server. Select the hardware you want to work with.
using a command prompt, open the projects folder and find the subfolder with your new project
open the folder in Visual Studio Code

code .

open pxt.json and edit the dependencies to use the file:... path instead of *

   dependencies: {
        "adafruit-metro-m0-express": "file:../../libs/adafruit-metro-m0-express"
   }

from the command line, set the PXT_NODOCKER environment variable to 1

export PXT_NODOCKER=1

run a local build that will create a CODAL checkout automatically. If you are missing tools, you will be notified by the build script.

pxt build --local --force

go to the built/dockercodal folder and open all CODAL in a new Visual Studio Code instance

cd built/dockercodal
code libraries/*

go to the Git tab in VS Code, and change the branch of the CODAL repository to work on to master. You can create a new branch to start doing your work and pull requests.
to build CODAL directly, run built/codal

python build.py

to rebuild your project from pxt, run pxt build --local --force from the project folder

Running

Run this command from inside pxt-maker to open a local web server

pxt serve

If the local server opens in the wrong browser, make sure to copy the URL containing the local token. Otherwise, the editor will not be able to load the projects.

If you need to modify the .cpp files (and have installed yotta), enable yotta compilation using the --localbuild flag:

pxt serve --localbuild

Updates

Make sure to pull changes from all repos regularly. More instructions are at https://github.com/microsoft/pxt#running-a-target-from-localhost

Repos

The pxt-maker target depends on several other repos. The main ones are:

https://github.com/microsoft/pxt, the PXT framework
https://github.com/microsoft/pxt-commmon-packages, common APIs accross various MakeCode editors
https://github.com/lancaster-university/codal-core, CODAL core project
https://github.com/lancaster-university/codal-mbed, mbed layer
https://github.com/lancaster-university/codal-samd21, CODAL SAMD21 layer
https://github.com/lancaster-university/codal-circuit-playground, Adafruit CPX layer

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

No vulnerabilities found.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

Security-Policy

Determines if the project has published a security policy.

10

License

Determines if the project has defined a license.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

8

Maintained

Determines if the project is "actively maintained".

7

Pinned-Dependencies

Determines if the project has declared and pinned its dependencies.

Reason

dependency not pinned by hash detected -- score normalized to 7

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/compress-images-on-pull-request.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/kalessine/sdmx-sax-parser/compress-images-on-pull-request.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/compress-images-on-pull-request.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/kalessine/sdmx-sax-parser/compress-images-on-pull-request.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pxt-buildpr.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/kalessine/sdmx-sax-parser/pxt-buildpr.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pxt-buildpr.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/kalessine/sdmx-sax-parser/pxt-buildpr.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pxt-buildtarget.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/kalessine/sdmx-sax-parser/pxt-buildtarget.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pxt-buildtarget.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/kalessine/sdmx-sax-parser/pxt-buildtarget.yml/master?enable=pin
Warn: npmCommand not pinned by hash: link.sh:1
Warn: npmCommand not pinned by hash: .github/workflows/pxt-buildpr.yml:24
Warn: npmCommand not pinned by hash: .github/workflows/pxt-buildpr.yml:25
Warn: npmCommand not pinned by hash: .github/workflows/pxt-buildtarget.yml:27
Warn: npmCommand not pinned by hash: .github/workflows/pxt-buildtarget.yml:28
Info: Dockerfile dependencies are pinned
Info: no insecure (not pinned by hash) dependency downloads found in Dockerfiles
Info: no insecure (not pinned by hash) dependency downloads found in shell scripts

0

Code-Review

Determines if the project requires code review before pull requests (aka merge requests) are merged.

Reason

GitHub code reviews found for 2 commits out of the last 30 -- score normalized to 0

Details

Warn: no reviews found for commit: 1439f19f93e7699d21b816a9b7ed60840b0d3924
Warn: no reviews found for commit: 7e09e2feb115c8fa8662ccb605a4c1d9955bb3a0
Warn: no reviews found for commit: df40e189ff4e4921436cf1e9b5a30352d2cad433
Warn: no reviews found for commit: f70ca92b8234e5184f1205b4a8b100aaefb9c176
Warn: no reviews found for commit: 66072c282035027ef01fa4e34c27d7c82203f4e8
Warn: no reviews found for commit: 0c5e05747df4fb93832899c49e3310fd430e01b0
Warn: no reviews found for commit: 6620fe19f4d39d04c718f1506eaebba9db450c7e
Warn: no reviews found for commit: 3687a29e68060bb645e6055f9106abc2b728256f
Warn: no reviews found for commit: 3329114c6ec7b74ba52ef3470ada9fa9c483ad43
Warn: no reviews found for commit: f512662cf0c554d3024149e5aed54c72471f8795
Warn: no reviews found for commit: a83e63084ddc173678d267803c0e4eee11aa39f2
Warn: no reviews found for commit: 20c70e406310fe67c1e43d0b40b7052da445c601
Warn: no reviews found for commit: 09b600641b00aeb2db79113633010f3b766df3dd
Warn: no reviews found for commit: ade73259a6551c5c1bf9ebafb064e1fcc05849fd
Warn: no reviews found for commit: af18eb35daf9a5f419b3043409c450904060aa14
Warn: no reviews found for commit: d7f15ded2564bfa35496a880769a40705c280ed9
Warn: no reviews found for commit: 255b38d15f9a7791855aef95abfbe2a71ed1921f
Warn: no reviews found for commit: b78a840c785f63a900911ba6e8031a70d2a82fa9
Warn: no reviews found for commit: a476d6d63d7abbbab6b1b3818a163e3eb0d25e7d
Warn: no reviews found for commit: e163046a0260f82f2e0ab6e099e2b25436196111
Warn: no reviews found for commit: 4c0859b4225a8c325a47725db6fbae4f94ff26cc
Warn: no reviews found for commit: 966a8240a043c8c6f4e98746a9391cc815c10e29
Warn: no reviews found for commit: 9814002b63e86601d186853c67f3d6debe8c2570
Warn: no reviews found for commit: 7fcee8a2224c8301beac3e0ee068ec2ccb1dacab
Warn: no reviews found for commit: 6e01dd95f96df909b797eeedddb3a16b9651f0d4
Warn: no reviews found for commit: 7f8d5859bff32ee050c341758021d070b0b60465
Warn: no reviews found for commit: e260057b6f5798fcbbcf451bb8e8c069a23354ad
Warn: no reviews found for commit: 4625187ab062a88a92ce007b73467e2a1c2448d7

0

CII-Best-Practices

Determines if the project has a CII Best Practices Badge.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Dependency-Update-Tool

Determines if the project uses a dependency update tool.

0

Fuzzing

Determines if the project uses fuzzing.

Score

5.1

/10

Last Scanned on 2022-08-15

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More