![](\"https:\/\/lh6.googleusercontent.com\/7wXgWXOsLqMSD_rwVu2VXFKHzB9jPc-dMUM9t5c058y-s0gIV91AuDxrpK3hb137zulryrG6QWTNBl_rYUIzQnMvTpZFc3phJOdZxScmLqc7rdLT_NlHWNTimBc9wN1doRvTeFAzibKBSfil0SVCrdN5c3cyyf8eiINazOOJqylW5FQgQXynasrxQ4I6\")
It supports Code.org’s Physical Computing module<\/a> that use the Adafruit Circuit Playground. <\/p>\n\n\n\n Code.org has researched benefits of physical computing which include:<\/p>\n\n\n\n Here is a timeline of the Code.org johnny-five fork:<\/p>\n\n\n\n It was time to upgrade because the version of serialport that the outdated johnny-five package was dependent on was causing pesky errors:<\/p>\n\n\n\n So the first task was to create a copy of the outdated johnny-five repo, name it johnny-five-deprecated and point all references in the main code-dot-org repo to it. Then I updated johnny-five to the latest release of its upstream v2.1.0.<\/p>\n\n\n\n I had to learn how to link the updated johnny-five locally with my local code-dot-org repo in order to develop and test Code.org customizations. The recommendation was to use Once I linked the two modules, I had build errors which required updates in webpack – fixing node dependencies and adding johnny-five to a list of packages that ship in ES6 and need to be transpiled for our purposes. A senior engineer to helped me with these updates.<\/p>\n\n\n\n Once I was able to build and then run the code-dot-org dashboard locally, I could finally start adding customizations, the reason why we forked johnny-five in the first place! There were three customizations I re-implemented:<\/p>\n\n\n\n Once these were implemented, I published to the NPM registry<\/a> and added the latest release on GitHub.<\/p>\n\n\n\n This was quite a challenging project overall, and I learned many lessons from it. The most important takeaway for me was that a good pull request tells a story. I relied upon notes and comments from Brad, a Code.org engineer who had done most of the prior work in johnny-five back in 2017-2018. His detailed notes guided me throughout the re-implementation process. I didn’t feel alone even though I was the only engineer assigned to this task.<\/p>\n\n\n\n I also appreciated that he included alternate paths he didn’t choose and explained why he didn’t choose certain options. <\/p>\n\n\n\n Overall, my journey with johnny-five presented many roadblocks and challenges, but ultimately, we were able to migrate successfully. Along the way, I learned many lessons and I’m proud to have contributed to the maintenance and support of the Code.org Maker Kit module whose future is looking bright!<\/p>\n\n\n\n I am 5 months into a 6-month software engineering internship at Code.org. The latest project I completed was the migration of our main code-dot-org repo from using an outdated fork of the johnny-five package that hadn’t been touched since January 2018 to the latest release of its upstream. johnny-five is an open source, firmata protocol […]<\/p>\n","protected":false},"author":12806,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-43","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/posts\/43","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/users\/12806"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/comments?post=43"}],"version-history":[{"count":10,"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/posts\/43\/revisions"}],"predecessor-version":[{"id":56,"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/posts\/43\/revisions\/56"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/media?parent=43"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/categories?post=43"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/fisheali\/wp-json\/wp\/v2\/tags?post=43"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![](\"https:\/\/lh5.googleusercontent.com\/qB1BrnD___RWpzSwpvzKzPv1aUvUj7xXA84Ufs8xVzKdgnoXgQU3_HytfsRXICBkK7CwKddUuG21wX6zzdyQJX7g_vNc_kZUi-u6pm-WEm3Vjq8nW_yZvusQHF7z6oFBfcMmBOCRs8bN8Ow7PLoXghGn4PeSGt84xGXHJGq6pmBZ2PzgftIW2Drw98r9\")
![\"\"](\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/6050\/files\/2022\/10\/Screen-Shot-2022-10-27-at-9.30.13-PM-1024x410.png\")
<\/figure>\n\n\n\n![](\"https:\/\/lh3.googleusercontent.com\/MY7Y3-Bfl05UbOlcBJPiGnkSmywU1kax1pbPAlQpHgLYpWByAG0Sy_6iYwSdXpyL3hmJcc8oPoLfx15F4OvubXEp0zjQvHCA5WAvdEyfUsb1bBLzRJpy2AJ4oasD1iphrvDMzu2Ho3PAcSdW-3U1Utn7Onjqk7rfozBEdZtqNfs4KkG1TWJu5Fc8GQtg\")
yarn link<\/code> or npm link<\/code>, but neither worked. So then I read online about yarn add<\/code> which adds a copy of the local repo as a node_module and that did the trick!<\/p>\n\n\n\n![\"\"](\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/6050\/files\/2022\/10\/Screen-Shot-2022-10-27-at-9.22.51-PM-1024x558.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/6050\/files\/2022\/10\/Screen-Shot-2022-10-27-at-9.25.02-PM.png\")
<\/figure>\n","protected":false},"excerpt":{"rendered":"