idea: replace require() calls with full component name
#130
Labels
Comments
|
yeah that's the plan, screws over dynamic requires but I can't see any practical use-cases for that on the client side anyway |
|
we don't need a require implementation at all if we do that it would just be |
|
Would still like a require implementation though since I require components outside the build, but I guess it'll be much simpler and could be opt in. |
|
didn't bother going with building the dep tree first, but that'll be the next optimization for sure |
|
Yeah I'm working on a "resolver" for both locals and dependencies. Want to wait until the registry is up though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ex:
Then don't even bother aliasing at all. All dependency checking will happen at build time. We can resolve the names based on the dependencies.
Only edge case i can think of is when users do
*with their dependencies, then we can resolve the dependency atrequire()time.Of course, this won't work with any components that do silly stuff with their require calls.
The text was updated successfully, but these errors were encountered: