Replies: 1 comment
-
@iljadaderko did you end up figuring out this set-up, and/or would you recommend a different route in 2022? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Sorry if this discussion ends up verbose, but this is my first experience with parcel and I am trying to figure out how to use it for a modern monorepo setup that targets browser / nodejs and exposes some shared modules.
start
andbuild
commands inapp/package.json
, so far so good. I then proceeded to set up aliases for these packages inside rootpackage.json
i.e.However when I tried to
import utilities from "core/utilities"
inside myapp
package, I got an error saying that this failed to resolve, so I assume I did something wrong here? I am also unable to use~/packages/core/utilities
, as it resolves incorrectly as well.target
for each of my packages now, but I am not sure if I shold do it in individual package json files or in root one, furthermore I want to somehow make it so that my app only produces code necessary to run it in latest chrome / safari and my server needs to produce bundles for node v14. In terms of where I want too build this, adist
folder for each package (i.e.packages/app/dist
) will work. Now how would I approach this to make it more managable?Would appreciate any examples / deep dives into this if possible. Need to understand how to set things like targets / engines / browserlist here correctly and produce modern bundles, while also utilising features like alias for better dev experience
Beta Was this translation helpful? Give feedback.
All reactions