-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Error: Failed to compile with 2 errors #18
Comments
@apasov My apologies for that. Everything should be good again. Please let me know right away. Thanks. |
You will need to upgrade to the latest @quasar/app v1.1.4 and the latest quasar-app-extension-qiconpicker v1.0.8 |
@apasov Please do this:
|
The demo is now live and having no issues: https://quasarframework.github.io/quasar-ui-qiconpicker/docs |
see my discord announcement: https://discordapp.com/channels/415874313728688138/552811775440060417/630418914655993876 |
I did as you suggested (delete node_modules etc.) but still there is By the way the demo says |
That is correct. @quasar/quasar-ui-qiconpicker = v1.0.3 and the @quasar/quasar-app-extension-qiconpicker = v1.0.8 @quasar/quasar-ui-qiconpicker is the actual component now. |
how about doing a |
If you would be so kind to unzip, |
I tested the project you created - it works properly. Mine not.
|
Are you using |
also
may give you more info about what's failing |
and you can remove
it's deprecated and the whole point of redoing the app extensions was to make them not dependent on each other. It was used by QIconPicker |
Yes, I'm using
What do you think of it? |
That is odd as that folder does not exist, however, it does exist here:
Let me investigate more |
Got nothing. I tried
on that project I gave you and it build (after commenting 'no-console' in eslintrc.js) |
I am thinking it has to do with some sort of caching. |
Caching? By I deleted all cache. |
go to folder // Util
import props from './utils/props' That's where the error is comping from, just wrong package // Util
import props from './utils/props.js' and rebuild (added .js) |
The other thing is you can delete your yarn cache, then delete node_modules, lock file, etc, then |
On Ubuntu, the yarn cache is in |
any status? |
Well, cleaning yarn cache didn't help. Mine was not so big as yours, just 1.5GB
This didn't fix the error as well. I also tried The only thing that worked is that I copied the What are your thoughts? |
No idea. That project I gave you worked, yet your existing one didn't. Kind of at a loss as to why. |
You're not importing in utils from anywhere are you? |
Oh, it was completely my fault. Yes, I was importing iconsets data directly from |
Ah, that makes sense now. :) Glad it got worked out. |
This is what I get after upgrading from v1.0.3 to v1.0.5 or v1.0.6
If I downgrade to v1.0.3 my project compiles okay.
The text was updated successfully, but these errors were encountered: