summaryrefslogtreecommitdiffstats
path: root/package.json
Commit message (Collapse)AuthorAgeFilesLines
* Add automatic JS license generation (#11810)silverwind2020-06-121-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | * Add automatic JS license generation Removed librejs file and replaced it with a plaintext file that is built from all JS dependencies that are included in the webpack build. It does not cover the few remaining statically vendored files and fomantic is added manually because it's not yet in the webpack build process. Fixes: https://github.com/go-gitea/gitea/issues/11630 * fix lint * remove jslicense, we're not librejs compatible any more * remove license.txt test as it depens on absent files * small optimization * trailing comma * localize and capitalize the word 'licenses' * reduce text to just 'Licenses' Co-authored-by: Lauris BH <lauris@nix.lv>
* Update JS dependencies (#11842)silverwind2020-06-111-12/+12
| | | Result of `make npm-update`, no noteworthy changes.
* Replace jquery-datetimepicker with native date input (#11684)silverwind2020-06-101-2/+0
| | | | | | | | | | | | This removes the jQuery plugin as well as the associated config options. Native input[type=date] does not require a language attribute as it is localized by default, except for the placeholder attribute for which I currently piggy-back the repo.issues.due_date_form localization option. Implementation should pretty much match GH. Of note is that Safari does not provide a UI for this input type, but I don't think providing one is neccessary and GH did not bother either. Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* rework eslint config (#11615)silverwind2020-06-091-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | * rework eslint config - use explicit config that only enables rules - upgrade eslint to 7.1.0 - add new plugins with selected rules enabled - fix discovered issues, remove global wipPrefixes * remove if * undo template change * add disabled rules as well for easier config updating * add missing disabled rule * update eslint and plugins * fix new violation * remove deprecated rules Co-authored-by: Lauris BH <lauris@nix.lv>
* Update fomantic-ui to 2.8.5 (#11736)silverwind2020-06-031-1/+1
| | | | | | Update to [2.8.5](https://github.com/fomantic/Fomantic-UI/releases/tag/2.8.5) and remove the workaround for the CSS build race condition. Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Move serviceworker to workbox and fix SSE interference (#11538)silverwind2020-05-211-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Move serviceworker to workbox and fix SSE interference Instead of statically hardcoding every frontend asset, this uses a type-based approach to cache all js,css and manifest.json requests. This also fixes the issue that the service worker was interfering with EventSource because it was unconditionally handling all requests which this new implementation doesn't. Fixes: https://github.com/go-gitea/gitea/issues/11092 Fixes: https://github.com/go-gitea/gitea/issues/7372 * rethrow error instead of logging * await .register * Revert "rethrow error instead of logging" This reverts commit 043162ba1f18b98a4bf9635959fd28d16e839fc5. * improve comment * remove JSRenderer * add version-based cache invalidation * refactor * more refactor * remove comment * rename item to fit cache name Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
* Move tributejs to npm/webpack (#11497)silverwind2020-05-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | * Move tributejs to npm/webpack - Move vendored bundle to npm and webpack - Rewrote initialization to single function - Restyled it (made it a bit smaller) - Fixed it for arc-green * fix mention * also include emoji on #content * Update web_src/less/_tribute.less Co-authored-by: mrsdizzie <info@mrsdizzie.com> * rewrite to only use one instance of Tribute * refactor * fix copy/paste error Co-authored-by: mrsdizzie <info@mrsdizzie.com> Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Remove IE11 support (#11470)silverwind2020-05-191-1/+3
| | | | | | | | | | | | | * Remove IE11 support With master now on 1.13, it's time to drop IE11 for good. The woff variants are also in use by Opera Mini but it has even less market share and I can only imagine how broken the UI is in it. Fixes: https://github.com/go-gitea/gitea/issues/6147 * update docs Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Update JS dependencies (#11412)silverwind2020-05-151-6/+6
| | | | | A bugfix for JS syntax in highlight.js and some misc updates.
* Switch code editor to Monaco (#11366)silverwind2020-05-141-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Switch code editor to Monaco This switches out CodeMirror for Monaco which is based on the same code base as VS code and should work pretty similar to it. It does add a few async chunks, totalling around 10MB to our build. It currently supports around 65 languages and in the default configuration, each language would emit one ugly [number].js chunk, so I opted to combine them all into a single file for now. CodeMirror is still being used under the hood by SimpleMDE so it can not be removed yet. * inline editorconfig, fix diff, use for markdown, remove more dead code * refactors, remove jquery usage * use tab_width * fix intellisense * rename function for clarity * misc tweaks, enable webpack progress display * only use --progress on dev build * remove useless borders in arc-green * fix typo * remove obsolete comment * small refactor * fix file creation and various refactors * unset useTabStops too when no editorconfig * small refactor * disable webpack's [big] warnings * remove useless await * fix dark theme check * rename chunk to 'monaco' * add to .gitignore and delete webpack dest before build * increase editor height * support more editorconfig properties * remove empty element filter * rename Co-authored-by: John Olheiser <john.olheiser@gmail.com>
* Update JS dependencies (#11297)silverwind2020-05-051-10/+10
| | | | | | | | Contains an apparently important bug fix for highlight.js [1], otherwise nothing of interest. [1] https://github.com/highlightjs/highlight.js/releases/tag/10.0.2 Co-authored-by: zeripath <art27@cantab.net>
* Update JS dependencies, min Node.js version 10.13 (#11246)silverwind2020-04-301-7/+7
| | | | | | | `less-loader` now dictates a minimum Node.js version of 10.13.0, released 2018-10-30 so I've updated this requirement to match. https://github.com/webpack-contrib/less-loader/releases/tag/v6.0.0
* Patch fomantic-ui to workaround build issue (#11244)silverwind2020-04-301-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * Patch fomantic-ui to workaround build issue Better workaround than https://github.com/go-gitea/gitea/issues/10653 for https://github.com/fomantic/Fomantic-UI/issues/1356. It does not seem like we're getting a new Fomantic-UI release anytime soon, so this patches it after node_modules installation. Fixes: https://github.com/go-gitea/gitea/issues/11243 Fixes: https://github.com/go-gitea/gitea/issues/10679 * copy instead of patch * update package-lock.json * Update Makefile Co-Authored-By: Sorien <Sorien@users.noreply.github.com> * Update web_src/fomantic/css.js Co-Authored-By: zeripath <art27@cantab.net> Co-authored-by: Sorien <Sorien@users.noreply.github.com> Co-authored-by: zeripath <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
* Update JS dependencies, highlight.js 10.0.0 (#11195)silverwind2020-04-241-4/+4
| | | | | | Breaking changes in higlight.js do not affect us. Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com> Co-authored-by: Lauris BH <lauris@nix.lv>
* Update JS dependencies (#11146)silverwind2020-04-201-14/+14
| | | | | Result of `make npm-update`. Some minor updates to build tools, no runtime dependencies affected.
* Upgrade jQuery to 3.5.0, remove jQuery-Migrate, fix deprecations (#11055)silverwind2020-04-181-2/+1
| | | | | | | | | | | | - Removed jQuery-Migrate as it seems to no longer be needed. - Removed a dead code section. - Fixed some deprecations detected by jQuery-Migrate. Ref: https://jquery.com/upgrade-guide/3.5/ Ref: https://github.com/gogs/gogs/search?q=repo-name-change-prompt Ref: https://github.com/go-gitea/gitea/search?q=repo-name-change-prompt Fixes: https://github.com/go-gitea/gitea/issues/9372 Co-authored-by: zeripath <art27@cantab.net>
* Move syntax highlighting to web worker (#11017)silverwind2020-04-131-1/+3
| | | | | | | | | This should eliminate page freezes when loading big files/diff. `highlightBlock` is needed to preserve existing nodes when highlighting and for that, highlight.js needs access to the DOM API so I added a DOM implementation to make it work, which adds around 300kB to the output file size of the lazy-loaded `highlight.js`. Co-authored-by: Lauris BH <lauris@nix.lv>
* Add 'make lint', restructure 'compliance' pipeline (#10861)silverwind2020-03-291-5/+5
| | | | | | | | | | - Added 'lint', 'lint-frontend', 'lint-backend' targets - Added 'lint-frontend', 'lint-backend' ci steps and restructure the 'compliance' pipeline to have a clear separation between frontend and backend and use parallelism where possible. Also, the main build pipelines now depend on 'compliance' so they will skip if it fails. - Added dependencies on ci steps so they skip when 'compliance' fails - Moved JS linters to devDependencies - Removed deprecated 'js' and 'css' targets
* Move JS build dependencies to 'dependencies' (#10763)silverwind2020-03-191-16/+16
| | | | | | | | | | | | | | - move all JS build dependencies to 'dependencies' - update all JS dependencies Reason for this is that npm will only install 'dependencies' when under the effect of NODE_ENV=production which may be present on some build systems. Linters currently need to be depdendencies because we run linting as part of the build step, but I plan to move them to a separate 'lint' target which means they can move to devDependencies then. Fixes: https://github.com/go-gitea/gitea/pull/10761
* move jquery-datetimepicker to npm/webpack (#10713)silverwind2020-03-171-0/+2
| | | | | | | | | - update to latest version and move to npm - adapt for api changes and css class rename - add specificity to arc-green rules as dependency css now loads later - use imports-loader to make it load correctly - fix some wrong paths in librejs Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Update JS dependencies (#10726)silverwind2020-03-141-9/+9
| | | | | Result of `make npm-update`. Only notable change is that `updates` now requires Node 10 and has been changed to a bundle, so its dependencies are now no longer installed.
* Move dropzone.js to npm/webpack (#10645)silverwind2020-03-071-0/+1
| | | | - unvendor dropzone and upgrade it from 4.2.0 to 5.7.0 - make `csrf` available on window.config
* Workaround fomantic build issue (#10655)silverwind2020-03-071-0/+1
| | | | | This blows up the fomantic CSS by around 500kB, but I see no other way. Ref: https://github.com/go-gitea/gitea/issues/10653
* Update JS dependencies (#10450)silverwind2020-02-251-9/+9
| | | | | | | | | | Fomantic's update process did fail to update via 'npm install' because of our config initially but it did work after manually bumping the version in semantic.json. Fomantic changes: https://github.com/fomantic/Fomantic-UI/blob/master/CHANGELOG.md#284
* move vue and vue-calendar-heatmap to webpack (#10188)silverwind2020-02-231-1/+3
| | | | | | | | | | | | - unvendor vue and vue-calendar-heatmap - remove unused moment.js leftover from previous heatmap version - ensure webpack loads the full version of vue - fix vue devmode warning related to 'searchLimit' type I wanted to name the chunk heatmap.js but adblockers don't like that filename [1]. [1] https://github.com/easylist/easylist/blob/3899d5dff33216c0bc64f09ff15d376f346d3e33/easyprivacy/easyprivacy_general.txt#L2095
* Add Octicon SVG spritemap (#10107)John Olheiser2020-02-111-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add octicon SVG sprite Signed-off-by: jolheiser <john.olheiser@gmail.com> * Static prefix Signed-off-by: jolheiser <john.olheiser@gmail.com> * SVG for all repo icons Signed-off-by: jolheiser <john.olheiser@gmail.com> * make vendor Signed-off-by: jolheiser <john.olheiser@gmail.com> * Swap out octicons Signed-off-by: jolheiser <john.olheiser@gmail.com> * Move octicons to top of less imports Signed-off-by: jolheiser <john.olheiser@gmail.com> * Fix JS Signed-off-by: jolheiser <john.olheiser@gmail.com> * Definitely not a search/replace Signed-off-by: jolheiser <john.olheiser@gmail.com> * Missed regex Signed-off-by: jolheiser <john.olheiser@gmail.com> * Move to more generic calls and webpack Signed-off-by: jolheiser <john.olheiser@gmail.com> * make svg -> make webpack Signed-off-by: jolheiser <john.olheiser@gmail.com> * Remove svg-sprite Signed-off-by: jolheiser <john.olheiser@gmail.com> * Update tests Signed-off-by: jolheiser <john.olheiser@gmail.com> * Missed a test Signed-off-by: jolheiser <john.olheiser@gmail.com> * Remove svg from makefile Signed-off-by: jolheiser <john.olheiser@gmail.com> * Suggestions Signed-off-by: jolheiser <john.olheiser@gmail.com> * Attempt to fix test Signed-off-by: jolheiser <john.olheiser@gmail.com> * Update tests Signed-off-by: jolheiser <john.olheiser@gmail.com> * Revert timetracking test Signed-off-by: jolheiser <john.olheiser@gmail.com> * Swap .octicon for .svg in less Signed-off-by: jolheiser <john.olheiser@gmail.com> * Add aria-hidden Signed-off-by: jolheiser <john.olheiser@gmail.com> * Replace mega-octicon Signed-off-by: jolheiser <john.olheiser@gmail.com> * Fix webpack globbing on Windows Signed-off-by: jolheiser <john.olheiser@gmail.com> * Revert Co-Authored-By: silverwind <me@silverwind.io> * Fix octions from upstream Signed-off-by: jolheiser <john.olheiser@gmail.com> * Fix Vue and missed JS function Signed-off-by: jolheiser <john.olheiser@gmail.com> * Add JS helper and PWA Signed-off-by: jolheiser <john.olheiser@gmail.com> * Preload SVG Signed-off-by: jolheiser <john.olheiser@gmail.com> Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: techknowlogick <matti@mdranta.net>
* move clipboard.js to npm/webpack (#10183)silverwind2020-02-081-0/+1
| | | | | | | | - created lazy-loaded webpack chunk for clipboard.js - upgraded clipboard.js from 1.5.9 to 2.0.4 - parallelize initialization of all lazy-loaded features Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com>
* update JS dependencies (#10155)silverwind2020-02-051-12/+12
| | | | result of `make npm-update`. no real notable changes, the breaking change in styleline is Node.js 10 which we already require.
* move jquery.are-you-sure to npm/webpack (#10063)silverwind2020-01-291-0/+1
|
* move highlight.js to npm/webpack (#10011)silverwind2020-01-281-0/+1
| | | | | | | | | | - introduced window.config to help with js-based lazy-loading - adjusted webpack chunk naming to avoid 'vendors~name.js' that webpack defaults to for vendor chunks. - added theme class to html and prefixed all selectors. this is neccesary so that the theme styles win over the lazy-loaded ones. Co-authored-by: zeripath <art27@cantab.net>
* move CSS build to webpack (#9983)silverwind2020-01-281-4/+4
| | | | | | | | | | | | | | - added new 'make webpack' target - deprecated 'make js' and 'make css' - extend webpack config to load the less files - updated docs I had to rename the source file of `arc-green.less` to avoid generating a useless JS entrypoint via webpack-fix-style-only-entries which would not work with different source/destination filenames. I hear that there should be cleaner solutions possible once we upgrade to Webpack 5. Co-authored-by: zeripath <art27@cantab.net>
* add css extraction and minification to webpack (#9944)silverwind2020-01-251-1/+5
| | | | | | | | | | | | | | This changes the CSS output of webpack to output to the public/css directory instead of inling CSS in JS. This enables CSS minification and autoprefixer based on browserslist which would otherwise not be possible. The result of this change is two new output files currently: - public/css/swagger.css - public/css/gitgraph.css Co-authored-by: techknowlogick <matti@mdranta.net>
* move jquery and jquery-migrate to npm/webpack (#9813)silverwind2020-01-211-0/+2
| | | | | | | | | | Currently, this needs to be its own chunk because fomantic depends on jQuery being present. The next step is to move fomantic to webpack too after which we can combine the index,fomantic and jquery files into one. jquery-migrate is still neccessary because our ancient version of Dropzone seems to break without it. I imagine it can be removed after a Dropzone upgrade.
* Use npm to manage fomantic and only build needed components (#9561)Lunny Xiao2020-01-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Use npm to manage fomantic * Only build needed semantic components * Fix make * Don't import fonts from google sites since we have loaded * [misc] devendor fomantic-ui and rebuild upon src or config changes only Signed-off-by: Jakob Ackermann <das7pad@outlook.com> * Change sort alphabetically of semantic components * Fix trailing slash * fix makefile * Remove dependency to gulp from package.json * Fix something * Simplife the makefile * add missed fomantic compnent Co-authored-by: Jakob Ackermann <das7pad@outlook.com>
* Add top author stats to activity page (#9615)Lauris BH2020-01-201-1/+5
|
* update supported browsers and add a few more (#9734)silverwind2020-01-161-4/+1
| | | | | | | | | Now includes Firefox ESR, Opera and a few more browser with usages between 0.5% and 1%. defaults resolves to > 0.5%, last 2 versions, Firefox ESR, not dead. Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com> Co-authored-by: zeripath <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* move swagger-ui to webpack/npm (#9714)silverwind2020-01-141-0/+3
| | | | | | Created a second webpack output file for swagger-ui which is loaded on the /api/swagger route. One notable difference is the absence of the swagger favicon that was previously used which is now the gitea icon. I see no easy way to restore that favicon, so I decided to not keep it.
* update js dependencies (#9676)silverwind2020-01-101-14/+14
| | | | | Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Update JS dependencies (#9255)silverwind2019-12-061-11/+11
| | | | This is the result of `make npm-update`. I also fixed a minor linting issue which came up with the eslint 6.7 update.
* Switch CSS minifier to cssnano (#9260)silverwind2019-12-051-1/+1
| | | | | This results in around 4kB saving in CSS size and also resolves with a particular issue on git bash which had issues with the format of the lessc arguments.
* Add Node.js build dep, remove built js/css files (#9114)silverwind2019-12-051-1/+1
| | | | | | | | | - Added Node.js as build dependency and removes build files from git. - Added version checks for both Go and Node.js. - Overhauled the js/css make target to only run when needed. - Merged the `generate` make target into `build` as per suggestion. Fixes: https://github.com/go-gitea/gitea/issues/6782 Fixes: https://github.com/go-gitea/gitea/issues/9216
* enable lazy-loading of gitgraph.js (#9036)silverwind2019-11-171-0/+4
| | | | | | | | | | | | | | | | | - moved gitgraph.js to web_src and made it importable and es6-compatible - created new webpack chunk for gitgraph - enabled CSS loader in webpack - enabled async/await syntax via regenerator-runtime - added script to ensure webpack chunks are loaded correctly - disable terser's comment extraction to prevent .LICENCE files gitgraph.js has many issues: 1. it is incompatible with ES6 because of strict-mode violations 1. it does not export anything 1. it's css has weird styles like for `body` 1. it is not available on npm I fixed points 1-3 in our version so it's now loadable in webpack. We should eventually consider alternatives.
* modernize js and use babel (#8973)silverwind2019-11-141-5/+12
| | | | | | | | | | | | | | * modernize js and use babel - add babel toolchain to transform modern JS to ES5 - extend eslint config for modern rules - fixes linting issues via `eslint --fix` and manual fixes * run 'make css' to satisfy CI * code style tweaks and set js indendation to 2 in .editorconfig * regenerate js
* Move index.js to web_src and use webpack to pack them (#8598)Lunny Xiao2019-11-131-1/+3
| | | | | | | | | | | | * Move index.js to web_src and use webpack * Fix initHeatMap * update eslint and move webpack to devDependencies * update index.js * add eslint env node
* Update JS dependencies (#8051)silverwind2019-09-021-3/+3
|
* update js dependencies (#7462)silverwind2019-07-141-3/+3
| | | this is the result of `make npm-update js css`
* update dependencies and various tweaks (#7344)silverwind2019-07-021-2/+6
| | | | | | | | | - ran `make npm-update` - ran `make js`, fixed new lint issue - ran `make css`, this added back some vendor prefixes - added `engines` property to package.json to specify minimum required Node.js version - added `private` property to package.json to prevent accidential publishing to npm
* replace lesshint with stylelint (#7305)silverwind2019-06-271-1/+2
| | | | | | | | | New CSS linter which is much more powerfull than the previous one. Configuration is default but I had to remove a few rules that were throwing too many or weird errors. More importantly, the linter will exit with code 1 on errors so now our build will fail if the CSS linter fails which should eliminate linter errors being introduced without notice.
* add 'npm' and 'npm-update' make targets and lockfile (#7246)silverwind2019-06-181-2/+3
| | | | | | | | | | | | | | | | | | * add 'npm' and 'npm-update' make targets and lockfile - `make npm` installs and updates node_modules, triggered automatically on `make css` and `make js` as it completes reasonably fast and ensures consistent modules. - `make npm-update` updates all dependencies to their latest version, regenerates `node_modules` from scratch and updates `package-lock.json`. It uses npm modules `updates` written by yours truly to find the latest version of each dependency. * add suggested make dependencies * remove package-lock.json during npm-update * regenerate package-lock.json
* remove and disable package-lock (#6969)silverwind2019-05-161-1/+1
| | | | | | | | | | | | | | | | * remove and disable package-lock Using exact versions in package.json has the same effect as lockfiles without all the troubles the lockfiles bring (different versions of package manager generating different lockfiles primarily). Ensured we only use exact versions in package.json and stopped generation of new lockfiles via .npmrc which is support by both the npm and yarn package managers. Fixes: https://github.com/go-gitea/gitea/issues/6967 * enable save-exact