-
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
Publish to NPM along with PrimeNG? #62
Comments
you can install it from github by adding the following dependency to your {
"dependencies": {
"primeng-sass-theme": "github:primefaces/primeng-sass-theme#16.5.0"
}
} npm will install the package from github based on the given tag or commit sha |
Sorry, should have clarified that the goal here is to support build environments that otherwise could consume primeng, but can't consume the themes directly out of github. An example would be a fully-airgapped system, or a CI that limits connections to an internal NPM proxy that performs dependency scanning/auditing work, but not arbitrary GitHub repos. |
Hello, Why and what are the reasons for not putting this GITHUB repository in an NPM package? |
Any news here? it will be really useful to have a npm package! |
fix for issue primefaces#62
Indeed, this would be quite useful |
For custom theming (and minimal theme changes, like overriding the default blue in bootstrap4-light-blue), the docs (https://primeng.org/theming#customtheme) and GH Discussions (https://github.com/orgs/primefaces/discussions/148#discussioncomment-7150183) currently recommend cloning this repository in order to access the SCSS files.
Could this package instead get published to NPM alongside primeNG, so my package.json can download both of them in tandem? This would also let corporate users continue to leverage internal NPM registry mirrors.
The text was updated successfully, but these errors were encountered: