he/him 
This is what Node doespic.twitter.com/owCHcvtpaK
Show this thread
When Rome is bundling and it finds an unknown import, it will tell you the exact spot that's unknown. In the screenshot shown, there is indirection happening in a package.json. Rome tells you that the problem is actually in the package.json main field, rather than your import.pic.twitter.com/ij2VwVq9xD
-
-
-
-
-
No other JS tool flags the problem correctly and the way the information is displayed isn't useful. More
actionable errors in JavaScript Show this thread -
Was the comparison with existing tools useful? Explicitly throwing shade is probably better than subtweeting. I don't want to seem antagonistic.
Show this thread
End of conversation
New conversation -
-
-
What is this and where can I get it?
- 1 more reply
New conversation -
-
-
Can Rome not only bundle cjs, but also esm?
- End of conversation
New conversation -
-
-
what would it take to have incremental bundling that you can rely on? I have to clear cache (parcel) from time to time to reflect the changes I made also this would enable incremental deploys for those static sites with 1000k subpages
-
It would take just using Rome. The caching model is that there’s a catchable build artifact per file which leads itself well to cache invalidation and incremental builds. The cache also doesn’t contain any absolute file paths so can be easily shared.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.