DX: start sapper project; configure eslint; eslint say that svelt should be dep; update package.json; build fails with crypt error; try to figure what the hell; google it; come here (if you have luck); revert package.json; add ignore error to eslint; Maybe we should offer better solution for this.

TBH It is a bit disheartening to see this issue closed when all proposed solutions do not sufficiently solve the issue at hand, I really like svelte but if this is how feature requests are handled I am probably not going to use it in the future.

I understand seeing a new warning is frustrating.

I don’t understand why we didn’t hear back from the Rails team on this.

Europe’s sweeping privacy rule was supposed to change the internet, but so far it’s mostly created frustration for users, companies, and regulators

Without this information, very likely your question will not be answered, frustrating both yourself and anyone else who does want to help, because they are unable to do so

I selected the WordPress smilie for an arrow so I could bring up the graphic with a couple of keystrokes, as opposed to adding an image.