[Draft] Spacewalk mykobo prototype phase 1

[gianfra-t]

Closes #17.

This PR contains the first steps of the prototype, with the requirements for Phase 1.

[github-actions]

yarn.lock changes

Summary

Status	Count
	20
	8
	1

Click to toggle table visibility

Name	Status	Previous	Current
@stellar/js-xdr		-	3.1.1
@stellar/stellar-base		-	11.0.1
@types/big.js		-	6.2.2
ansi-escapes		6.2.0	6.2.1
axios		-	1.6.8
base32.js		-	0.1.0
base64-js		-	1.5.1
big.js		-	6.2.1
bignumber.js		-	9.1.2
buffer		-	6.0.3
eventsource		-	2.0.2
follow-redirects		-	1.15.6
husky		8.0.3	9.0.11
ieee754		-	1.2.1
lint-staged		15.2.0	15.2.2
listr2		8.0.0	8.0.1
node-gyp-build		4.6.0	4.8.0
npm-run-path		5.1.0	5.3.0
proxy-from-env		-	1.1.0
randombytes		-	2.1.0
rfdc		1.3.0	1.3.1
sha.js		-	2.4.11
sodium-native		-	4.1.1
stellar-base		-	11.0.1
stellar-sdk		-	11.3.0
string-width		7.0.0	7.1.0
toml		-	3.0.0
type-fest		3.13.1	0.21.3
urijs		-	1.19.11

[TorstenStueber]

Thanks, nicely done.

Please change this PR so that it does not merge into main, but into some special branch that we use for the prototype, as specified in the original ticket (there I proposed offramp-prototype).

This is just a prototype, so none of the following statements really matter for this code base. However, I want to already leave a few general comments as a reference for a future actual production implementation.

• To be consistent with our style and to adopt common TypeScript conventions, don't prefix Interfaces with "I", just use the normal name.
• I think we should optimize for colocation, particularly when it comes to CSS and therefore don't put the CSS code in an extra file; in my opinion the CSS framework that maximizes colocation is Tailwind.
• Most components will then only be a single file -> in this case I think we should not put them into an index.ts file inside a folder but keep it flat. At least when editing it is much easier to find a file just looking at the name on the tab.
• This PR replaces bn.js with big.js. Polkadot.js already comes with bn.js, no need to add yet another big number library (parsing numbers with decimals is also straightforward without any libraries). We should strive to keep our npm dependencies as minimal as possible to lower the attack surface and keep the build small.

[TorstenStueber]

Absolutely!

[ebma]

I'm merging this already in order to be able to establish a good structure for branches and deployments. Let's address the comments in the next iterations.