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
When I bundle this library in my project, I get the following warning
WARNING in ./node_modules/filer/dist/filer.min.js 1:292-296
Critical dependency: the request of a dependency is an expression
@ ./app/elements/REPLList.js 2:0-34 5:11-23
@ ./app/index.js 3:0-46 4:107-115
It seems to be due to how Parcel bundles and exposes a require() where the path is an expression (at filer.min.js 1:292-296 you'll find require(t) instead of require('string')).
While I've found a workaround for the moment, it's annoying and hacky. It seems like Parcel 2 fixes this? Was wondering if filer would eventually upgrade to Parcel 2?
The text was updated successfully, but these errors were encountered:
@joshuali7536 sounds good. NOTE: the use of parcel is not critical here. Ideally the move to Parcel 2 should be the easiest thing to do (start with that); but if moving to rollup or something else is easier, I'd be open to that too. The goal here is, "no security issues in the bundling toolchain..."
When I bundle this library in my project, I get the following warning
It seems to be due to how Parcel bundles and exposes a
require()
where the path is an expression (atfiler.min.js 1:292-296
you'll findrequire(t)
instead ofrequire('string')
).While I've found a workaround for the moment, it's annoying and hacky. It seems like Parcel 2 fixes this? Was wondering if filer would eventually upgrade to Parcel 2?
The text was updated successfully, but these errors were encountered: