Fabrizio Ferrai

An update on this now that we have the new codebase in place (see the `spaghetto` folder). This command would: - produce a [Manifest](https://github.com/purescript/registry-dev/blob/0bad5ddded9ca7d8f3e461588aa92a05df9125b1/src/Registry/Schema.purs#L21) for the selected package - run...

Thanks for opening this @joneshf! I'm certainly open to discuss the matter, and even merge a patch for this. My only wish in this case is that you'd available to...

@joneshf sorry, I somehow missed the notification on this one - thank you for the ping. I have only one question about the change you propose: would defining another `bin`...

I'm also fine with any name, as long as it doesn't start with `spago` - this is so that we don't mess up with shell autocompletion and accidentally confuse users...

I think what I meant to say was: are you able to use any workaround for this or is it just broken and there's no workaround?

> The only workaround I can think of would be someone maintaining another npm package that provided a "normal" bin. Right - I am not very excited about having another...

@joneshf I'd merge a PR that: - copies over the `npm` directory to another one with the code for the new package - updates the CI code to deploy the...

@maralorn I'd happily merge a patch with the updates if you'd like to have a go at this! Otherwise I'll take care of it, but it might take a while...

Hi @srghma! I can reproduce the first problem you reported, and it's a bug in this line: https://github.com/spacchetti/spago/blob/8ce19ea5648f8bd65d6db88428bac56e66cf2560/src/Spago/Config.hs#L115 The way we should fix it is that we should call `makeAbsolute`...

I feel that caching the `output` folder is likely to not be a safe thing to do at least whenever the compiler version changes. A very-closely-related ticket we have about...