-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't resolve 'Fabric/fabric.require' in node_modules. #82
Comments
Apperently i fixed the former issue. Now it's given me the: ERROR in ./node_modules/fabric/dist/fabric.require.js Anyone know if it's the HttpModule -> HttpClientModule thingy that Angular was going through version 5 to 6? |
"Fixed" the problem by replacing |
this seems to be a work-around |
how to resolve it? |
This issue is very annoying. How can I solve this using yarn? |
@Fridthjof 's solution worked for me, I also modified the fabric.js file. |
@hestellez what did you change in fabric.js? |
The solution here and in documentation didn't work for me, unfortunately. |
Inside node modules, I don't know If there are problems when deploying, but it let me work for the moment |
I got the same issue when I tried to install it, and this command solved the issue! |
There is no Could somebody finally please fix this? The suggested workarounds did not help in my case. |
This is because the postinstall command in package.json in the currently published version installs fabric version ^3.3.2, in which there is no Fortunately, this seems to have been patched in |
Here's a workaround: add the following to your
Or the following if using
(The This is not really an ideal solution as the wrong version of |
We'll release the fix for #286, next week |
It was released in v3.7.3. |
Module not found: Error: Can't resolve 'fabric/dist/fabric.require' in '.\node_modules\tui-image-editor\dist'
I've already looked at former issues with fabric, these are not fixing the problem.
Version
"tui-image-editor": "^3.2.2"
Angular 6.1.0
Node 8.11
Tried with fabric 1.6.7 and 2.4.2
The text was updated successfully, but these errors were encountered: