Re: NodeJS help: updating python-pydata-sphinx-theme
On 4/11/22 17:45, Sandro Mani wrote: > Facing a similar situation a while ago, it was suggested to use a script > like [1] to prepare an offline cache of all dependencies, and point yarn > to that folder in the package spec. Other example is pgadmin4 [2]. > > Sandro That only works if that folder only contains actual source code. It does not work if the folder contains minified JavaScript and/or CSS, which is not source code. -- Sincerely, Demi Marie Obenour (she/her/hers) OpenPGP_0xB288B55FFF9C22C1.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: NodeJS help: updating python-pydata-sphinx-theme
On Mon, Apr 11, 2022 at 3:45 PM Sandro Mani wrote: > Facing a similar situation a while ago, it was suggested to use a script > like [1] to prepare an offline cache of all dependencies, and point yarn > to that folder in the package spec. Other example is pgadmin4 [2]. > > Sandro > > [1] https://src.fedoraproject.org/rpms/qgis/blob/rawhide/f/prepare_vendor.sh > [2] https://src.fedoraproject.org/rpms/pgadmin4/tree/rawhide Excellent! Thank you, Sandro. That looks like exactly what I need. -- Jerry James http://www.jamezone.org/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: NodeJS help: updating python-pydata-sphinx-theme
Facing a similar situation a while ago, it was suggested to use a script like [1] to prepare an offline cache of all dependencies, and point yarn to that folder in the package spec. Other example is pgadmin4 [2]. Sandro [1] https://src.fedoraproject.org/rpms/qgis/blob/rawhide/f/prepare_vendor.sh [2] https://src.fedoraproject.org/rpms/pgadmin4/tree/rawhide On 11.04.22 23:41, Jerry James wrote: The latest version of python-networkx requires version 0.8 or later of python-pydata-sphinx-theme to build its documentation. That version of python-pydata-sphinx-theme needs 3 new python packages, which I can handle, but it also comes with a new requirement: using node to build the theme files (CSS and JavaScript). I ran a mock build with --enable-network. The build downloaded 759 node modules, all so that it can embed 2 of them (bootstrap and popper.js) in the theme files. There are only 25 direct node dependencies (see below), so I assume the other 734 are transitive dependencies. The guidelines (https://docs.fedoraproject.org/en-US/packaging-guidelines/Node.js/) suggest that I need to add 759 Source tarballs, which is a non-starter. Is there a realistic way to handle this situation? Direct node dependencies: @fortawesome/fontawesome-free (which we unbundle) bootstrap clean-webpack-plugin copy-webpack-plugin css-loader dedent extract-loader file-loader html-webpack-plugin imports-loader jquery mini-css-extract-plugin node-sass optimize-css-assets-webpack-plugin pa11y-ci pa11y-ci-reporter-html popper.js sass-loader style-loader webpack webpack-cli webpack-dev-server webpack-merge webpack-shell-plugin webpack-watch-files-plugin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
NodeJS help: updating python-pydata-sphinx-theme
The latest version of python-networkx requires version 0.8 or later of python-pydata-sphinx-theme to build its documentation. That version of python-pydata-sphinx-theme needs 3 new python packages, which I can handle, but it also comes with a new requirement: using node to build the theme files (CSS and JavaScript). I ran a mock build with --enable-network. The build downloaded 759 node modules, all so that it can embed 2 of them (bootstrap and popper.js) in the theme files. There are only 25 direct node dependencies (see below), so I assume the other 734 are transitive dependencies. The guidelines (https://docs.fedoraproject.org/en-US/packaging-guidelines/Node.js/) suggest that I need to add 759 Source tarballs, which is a non-starter. Is there a realistic way to handle this situation? Direct node dependencies: @fortawesome/fontawesome-free (which we unbundle) bootstrap clean-webpack-plugin copy-webpack-plugin css-loader dedent extract-loader file-loader html-webpack-plugin imports-loader jquery mini-css-extract-plugin node-sass optimize-css-assets-webpack-plugin pa11y-ci pa11y-ci-reporter-html popper.js sass-loader style-loader webpack webpack-cli webpack-dev-server webpack-merge webpack-shell-plugin webpack-watch-files-plugin -- Jerry James http://www.jamezone.org/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure