undefined | Better HN

0 pointsthesmallestcat9y ago0 comments

Maybe it's because of:

> half the dependencies on the web out there crash immediately because they decided you have to import React and Component from "react" instead of "react-native" now.

That resonates for anybody who has done serious work with npm packages over the past few years. It seems like horrific breakage is the norm. Package authors break backwards compatibility for the stupidest "improvements."

0 comments

dikaiosune9y ago

So please correct me if I'm wrong, but aren't these papercuts the exact motivating reason for something like Exponent?

dismantlethesun9y ago

Isn't there a way to control module name resolution when compiling a react-native app? On the browser side we have JSPM and Webpack, which let you alias module names so you don't have to rewrite third party code.

It's pretty useful too if you have a drop-in replacement for another library. Heck with JSPM, you can even scope module resolution per module... so you can say module A should resolve to B but only within the context of an import from module C, everything else gets the normal resolution.

j / k navigate · click thread line to collapse