All the rest of the changes are due to a merge from master from the original repo. (I did this as a merge instead of a rebase, mostly because I've been experimenting.)
I'm open to other approaches, eg. rebasing, or pulling into your repo from master (which requires some permissions to me), or... whatever.
The only remaining task before merging is to deploy this to my test server and put it through the paces (which I'll do today), but I expect no issues since npm run build and npm run serve already worked.
This includes the following tiny fixes:
* a [fix for the contact-download](https://gitea.anomalistdesign.com/trentlarson/crowd-funder-from-jason/commit/0fbd1ad51a9b383b9935b62868d0d354b5985bf4)
* a [change to avoid an on-screen error on localhost](https://gitea.anomalistdesign.com/trentlarson/crowd-funder-from-jason/commit/2ae165d56fb9decbeb608872e06896e00abc6731)
* a [change to avoid a console error in a common case](https://gitea.anomalistdesign.com/trentlarson/crowd-funder-from-jason/commit/78fab735e6bb331f0e3b7554bbc7edcefeda1f39)
All the rest of the changes are due to a merge from master from the original repo. (I did this as a merge instead of a rebase, mostly because I've been experimenting.)
I'm open to other approaches, eg. rebasing, or pulling into your repo from master (which requires some permissions to me), or... whatever.
The only remaining task before merging is to deploy this to my test server and put it through the paces (which I'll do today), but I expect no issues since `npm run build` and `npm run serve` already worked.
Note that I changed the default to report lint errors and not fix them, with a separate command to fix them. (I don't mind making "fix" the default as long as we have some command that only reports.)
OK, I added some linting fixes.
Note that I changed the default to report lint errors and not fix them, with a separate command to fix them. (I don't mind making "fix" the default as long as we have some command that only reports.)
Houston, we have a problem: the vite.config.js is not fully applied on npm run build: the Help page doesn't show a git hash and the sw_scripts-combined.js file is not created and copied into the dist directory.
Houston, we have a problem: the vite.config.js is not fully applied on `npm run build`: the Help page doesn't show a git hash and the sw_scripts-combined.js file is not created and copied into the dist directory.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This includes the following tiny fixes:
All the rest of the changes are due to a merge from master from the original repo. (I did this as a merge instead of a rebase, mostly because I've been experimenting.)
I'm open to other approaches, eg. rebasing, or pulling into your repo from master (which requires some permissions to me), or... whatever.
The only remaining task before merging is to deploy this to my test server and put it through the paces (which I'll do today), but I expect no issues since
npm run buildandnpm run servealready worked.OK, I added some linting fixes.
Note that I changed the default to report lint errors and not fix them, with a separate command to fix them. (I don't mind making "fix" the default as long as we have some command that only reports.)
Houston, we have a problem: the vite.config.js is not fully applied on
npm run build: the Help page doesn't show a git hash and the sw_scripts-combined.js file is not created and copied into the dist directory.