feat: goodbye noir-starter, hello noirenberg

[signorecello]

Problem

Noir and BB versions were hard to sync. After some discussion, we agreed that there could be a tool to check the correct bb version for the wanted noir version.

As it wouldn't live inside the noir repository or even inside the noir-lang org (check #88), we thought it could have a creative name.

Description

Starts a refactor by extending the existent npx script to do this installation and check. It also moves it to ts using the excellent bun and tsx tooling.

I reckon I went a bit overboard with the dependencies on ora but I also wanted it to look good!

Next steps

• This repo needs to be moved as of Migrate repository to AztecProtocol #88
• It should also be renamed
• It could help ease some of the annoyances between nargo and bb that we have already identified and agreed. But I'll spike those and discuss internally first

[netlify]

✅ Deploy Preview for noir-vite-hardhat canceled.

Name	Link
🔨 Latest commit	b4ca59b
🔍 Latest deploy log	https://app.netlify.com/sites/noir-vite-hardhat/deploys/66fbd75fae606c0008e33cfe

[signorecello]

btw since this repo doesn't use release-please yet, you can actually already try the script with npx noirenberg as I have already published it

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher

🚮 Removed packages: npm/@inquirer/[email protected], npm/@inquirer/[email protected], npm/@inquirer/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[Savio-Sou]

Flagging that I'm not sure if / when @TomAFrench might plan to deprecate this script from Noir, which could break this noirenberg script here.

[Savio-Sou]

Given how there is no good way to source Noir compatibility from within Barretenberg yet, don't think this should be blocking.

[TomAFrench]

Oh yeah, this script is purely an implementation detail of the noir repo CI and we don't provide any guarantees about its stability.

[Savio-Sou]

Note that hosting the noirenberg installation script in a standalone AztecProtocol repo (instead of as a part of the starter / boilerplate repo) might make more sense.

[critesjosh]

Cool tool! I think you need to update the README as well.

Do you publish updates to noirenberg directly from this repo? Is this repo the best home for this tool? It feels unrelated to a Noir stater repo, and not something that I'd necessarily want to clone when starting a noir project.