You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current version of the Webpack resolver is a hand-rolled minimum-viable-product that satisfied my initial needs, but given #181, #165, #135, #134, #164, seems like it would be better to integrate more directly with Webpack's internals, to avoid drift.
Need to
investigate how feasible this is. (I looked briefly before, seemed fairly involved)
find necessary pieces by locating a sibling webpack package and then interacting with its dependencies from there (to avoid installing a parallel, incompatible version of enhanced-resolve, etc)
version the resolver in some way matching the version of Webpack with which it was developed/verifed?
The text was updated successfully, but these errors were encountered:
Current version of the Webpack resolver is a hand-rolled minimum-viable-product that satisfied my initial needs, but given #181, #165, #135, #134, #164, seems like it would be better to integrate more directly with Webpack's internals, to avoid drift.
Need to
webpack
package and then interacting with its dependencies from there (to avoid installing a parallel, incompatible version ofenhanced-resolve
, etc)The text was updated successfully, but these errors were encountered: