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
{{ message }}
This repository has been archived by the owner on Dec 6, 2022. It is now read-only.
The import of most components from popular library antd break the application compilation with following error:
/home/scandiweb/Projects/create-scandipwa-app/node_modules/antd/es/date-picker/generatePicker/generateSinglePicker.js
Attempted import error: 'Components' is not exported from '../../../../../runtime-packages/csa-blank/src'.
The file it is referring to, contains following import declaration:
import { getTimeProps, Components } from '.';
If I change it to ./index.js then it works. The question is what is causing the setup to assume that such import . is pointing to ../../../../../runtime-packages/csa-blank/src. The thing is - it is coming such way into the fallback plugin, we do not intercept this request (which is expected).
The resolver's hook resolve arguments request and resolveContext are already containing this value, not the expected ..
Expected behavior
I am, honestly speaking, unsure if this is expected or not. I have not seen the issues like that reported antd library, thus I assume that issue is something to deal with our setup. I was unable to research where does it came from.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
The import of most components from popular library
antd
break the application compilation with following error:The file it is referring to, contains following import declaration:
If I change it to
./index.js
then it works. The question is what is causing the setup to assume that such import.
is pointing to../../../../../runtime-packages/csa-blank/src
. The thing is - it is coming such way into the fallback plugin, we do not intercept this request (which is expected).The resolver's hook
resolve
argumentsrequest
andresolveContext
are already containing this value, not the expected.
.Expected behavior
I am, honestly speaking, unsure if this is expected or not. I have not seen the issues like that reported
antd
library, thus I assume that issue is something to deal with our setup. I was unable to research where does it came from.The text was updated successfully, but these errors were encountered: