Feat/conf file

[SamTV12345]

This adds support for config files. You can now adapt your local conf file with craft :)

• Just run craft config get to retrieve a key, --json is also supported
• craft config set key value to set a key value combination
• craft list to list all configured things

[shahen94]

@SamTV12345 Why naming fields & vars pnpm ?

[SamTV12345]

@SamTV12345 Why naming fields & vars pnpm ?

That's the big question. Do we strive to replace pnpm then we probably need to obey the things pnpm does. Other than that we could also roll our own thing and hope it will work and get adoption. It's the same with the other variables. Will we get adoption if someone needs to rework his entire setup. It's like a marketing decision 🙂

[shahen94]

That's a good question 🤔

At least we'll need to have craft working by itself initially. Then, we can have adapters for lock files to parse it for each package manager(npm, yarn v1.*, pnpm) later. (example: https://github.com/yarnpkg/berry/blob/master/packages/plugin-pnpm/sources/PnpmLinker.ts#L14)

This was a busy month. In case of any updates, I'll respond faster then

[SamTV12345]

That's a good question 🤔

At least we'll need to have craft working by itself initially. Then, we can have adapters for lock files to parse it for each package manager(npm, yarn v1.*, pnpm) later. (example: https://github.com/yarnpkg/berry/blob/master/packages/plugin-pnpm/sources/PnpmLinker.ts#L14)

This was a busy month. In case of any updates, I'll respond faster then

Alright :) Yes let's just get craft to work on its own. I saw that pnpm also offers migrations for the lockfiles of other languages. Can we merge this or are there things left to do with this pr?

[shahen94]

@SamTV12345 Yes, let's merge this, just please fix the conflict

[SamTV12345]

I'll solve the merge conflicts tomorrow so we can move on with the next topic.

[shahen94]

Perfect, ty!