Skip to content

Conversation

@simonra
Copy link
Member

@simonra simonra commented Jul 13, 2024

It was really useful. It should be there when we inevitably copy paste this project for our next production!

simonra added 2 commits July 13, 2024 17:59
For some reason, the absence of this, has yet again this year, resulted
in an ancient renin from registry.yarnpkg.com being picked up. I mean,
if we encouraged by running with just refferingto renin in package.json
and that was it, I'd get it. But since we require renin being in a sibling
folder anyway, this is just a source of pain. And this should fix it. For
now.
@simonra
Copy link
Member Author

simonra commented Jul 13, 2024

In the spirit of reducing chances to trip up, I've also tweaked the reference to Renin in the packages.json file, for the reasons stated in the commit message, which are:

For some reason, the absence of this, has yet again this year, resulted in an ancient Renin from registry.yarnpkg.com being picked up. I mean, if we encouraged by running with just referring to Renin in package.json and that was it, I'd get it. But since we require Renin being in a sibling folder anyway, this is just a source of pain. And this should fix it. For now.

})
);

// @ts-ignore
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a fan of all the ts-ignores. What is it complaining of?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants