-
Notifications
You must be signed in to change notification settings - Fork 84
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 during the build on version 17.12.0 #117
Comments
Hi, I have checked the file and exists the variable in the line 58 Did you upgrade your library? |
Hello, Thank you |
I have checked the dark and the line is included too: Maybe I'm checking in the wrong place. Could you confirm @cetincakiroglu if this problem exists or if i'm in the correct file. If not tell me what is the file and I can make the PR |
Same issue here. @SoyDiego it seems that what gets installed via NPM is not the same as the source files (both themes, version Perhaps an issue in your publish process? |
Are you using NPM to install it? |
Indeed, I'm using NPM 10. And I thought I could simply install the
But as I can see, there are some differences between the source code and the code that gets "installed" using NPM. As I said, this was my initial idea to reduce the manual work in maintaining the theme in sync with PrimeNG. In fact, it seems I'm not the only one who wants to avoid this manual work: #62 Do you think this is something the PrimeNG team can have a look at? At least ensuring that installing via |
Maybe this PR makes it work? #113 |
Digging a bit more into this, I think there is a mismatch in the tag And there is a newer commit in the So I guess it's just matter or replacing the latest |
I'm not part of Primetek only a contributor but I think they are not interested (I don't remember why in create a NPM package, maybe i'm wrong, I don't know 100%). |
If I understood ok, maybe they created the tag before this commit. Will see if generating a new tag, the problem is solved. We need to wait for Primetek team |
Yeah, that's right. Fortunately in the meantime I can simply add the commit hash to get the latest changes:
|
That's good alternative idea at the moment. Thanks for share it |
Hello,
I just upgraded the library version to 17.12.0. I'm using the lara-cyan theme and I encountered the following error during the build:
Undefined variable.
21 │ outline-offset: $inputFocusOutlineOffset;
node_modules/primeng-sass-theme/theme-base/_mixins.scss 21:21 focused-input()
node_modules/primeng-sass-theme/theme-base/components/input/_autocomplete.scss 22:13
@import node_modules/primeng-sass-theme/theme-base/_components.scss 10:13
@import node_modules/primeng-sass-theme/themes/lara/lara-dark/cyan/theme.scss 13:9
It appears that the variable does not exist in the _variables.scss file of that theme. Could you please take a look?
Thank you very much and best regards.
The text was updated successfully, but these errors were encountered: