Resolve import paths?

#1

I’d like to set up my code so I don’t have to write import statements like import X from '/client/modules/atoms/X' and import Y from '../../../atoms/Y'.

I’ve heard of Webpack and found this forum post to use Webpack and this blog post on resolving, but I’m still confused. It’s also a concern that the webpack:webpack project is no longer maintained.

I tried adding the webpack package and adding lines similar to what the blog recommended, but I get a conflict from ecmascript. So I removed that, but then it wants an entrypoint, which I currently don’t have, nor do I want to take all that time to set one.

How can I accomplish this easily and quickly?

1 Like
#2

I wonder if using https://atmospherejs.com/webpack/webpack and the aliases will work?