-
Notifications
You must be signed in to change notification settings - Fork 261
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
a plugin for *.less was active when it was published but none #366
Comments
Same error here but i fixed it doing the following:
|
Still the same =(...I think I just forget about it, thanks anyway |
Same issue |
+1 - Same issue Tried the steps suggested by @jc2 above, but it didn't help:
=> Started proxy. While building for web.browser: => Your application has errors. Waiting for file change.
Changes to your project's package version selections: aldeed:tabular removed from your project yogiben:admin: removed dependency
Changes to your project's package version selections: aldeed:tabular added, version 1.4.2 yogiben:admin: A complete admin dashboard solution
=> Started proxy. While building for web.browser: => Your application has errors. Waiting for file change. |
have you tried a meteor reset after remove yogiben:admin? |
I just tried and it didn't help:
See the results (including versions info - meteor --version && node -v && npm -v) below: meteor-admin-lte > meteor => Started proxy. While building for web.browser: => Your application has errors. Waiting for file change. meteor-admin-lte > meteor remove yogiben:admin Changes to your project's package version selections: aldeed:tabular removed from your project yogiben:admin: removed dependency meteor-admin-lte > meteor reset meteor-admin-lte > meteor update less meteor-admin-lte > meteor add yogiben:admin Changes to your project's package version selections: aldeed:tabular added, version 1.4.2 yogiben:admin: A complete admin dashboard solution meteor-admin-lte > meteor => Started proxy. While building for web.browser: => Your application has errors. Waiting for file change. meteor-admin-lte > meteor --version && node -v && npm -v meteor-admin-lte > |
+1 |
Check your less version number manually in .meteor/versions. |
Yes, meteor didn't update less to the latest version. I've removed less again and re-installed with specific version - it worked this way and the issue has been resolved:
FYI - my configuration:
Thank you. |
Hi Leonid, From which directory should I run remove and add less commands? |
@brascene use those commands in your meteor project (where you use "meteor" to run the project) |
@jc2 Thank you! Thing was that I don't need to "meteor remove less", just "meteor add [email protected]" and it's all set up. |
Fresh meteor install based on : After update of Less ( with fresh of meteor, less is 1.0 ), meteor-admin seem to work... maybe need more test. Updated documentation, I suppose is important. |
Just as a matter of interest, when I first came across this package, I created a bare app and tried to add less then. For some bizarre reason it only adds less 1.0.0 to bare versions. Despite forcing a package update.. Like this for example:
It appears that meteor doesn't always pick up when a few of the packages are out of date as quite a few of those are old. You'll need to force a full update with Something else I haven't seen checked is peoples global npn caches. I still forget I have the odd module in them from time to time and spend a while frustrated at something like that. I'm not sure if this helps, but it's saved me a lot of nightmares in the past, but Just to show you quickly:
Hope this helps someone out... Great work by the way... Nifty!.. |
Hi,
I have this error, please advice:
Errors prevented startup:
While building for web.browser:
error: no plugin found for lib/client/css/admin-custom.less in yogiben:admin; a plugin for *.less was active when it was published but none
is now
The text was updated successfully, but these errors were encountered: