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
$ parcel build ./src/index.js
🚨 /xyz/project/src/index.js: Cannot resolve dependency './../../../service-worker.js' at '/service-worker.js'
at /xyz/project/node_modules/browser-resolve/node_modules/resolve/lib/async.js:55:21
at load (/xyz/project/node_modules/browser-resolve/node_modules/resolve/lib/async.js:69:43)
at onex (/xyz/project/node_modules/browser-resolve/node_modules/resolve/lib/async.js:92:31)
at /xyz/project/node_modules/browser-resolve/node_modules/resolve/lib/async.js:22:47
at FSReqWrap.oncomplete (fs.js:166:21)
💁 Possible Solution
I have no idea, in another project with the same setup, this bug never hit me.
🌍 My Environment
Software
Version(s)
Parcel
1.4.1
Node
9.2.1
Yarn
1.3.2
OS
OS X Yosemite 10.10.5
The text was updated successfully, but these errors were encountered:
U can use a relative path, or you could wait untill absolute paths get supported (It's not unrelated as the worker.js's code should end up in the dist folder like anything else...)
Duplicate of #86 and #336
I don't think this is a duplicate. The core issue is that parcel tries to resolve string that looks like file path when it shouldn't do it. It should leave this string as is.
I'm seeing this issue now. Is there any workaround?
🐛 bug report - Attempts to resolve unrelated string
🎛 Configuration (cli command)
🤔 Expected Behavior
Parcel should not attempt to resolve random JS strings just because they look like paths.
😯 Current Behavior
File Structure:
src/index.js:
Error:
💁 Possible Solution
I have no idea, in another project with the same setup, this bug never hit me.
🌍 My Environment
The text was updated successfully, but these errors were encountered: