Here's the first stab at the vitejs refactor. I'm not completely done testing. When I start it up, I get the below screenshot with an error notification, Could not set notifications., so I could have messed something up.
I also see App.vue:346 Got vapid key: in the browser console... which may just be an error in my local configuration.
To start the vite development server run:
npm run dev
The other big difference was having to change environment variables. Instead of VUE_APP_, the prefix is now VITE_.
So, we'll need to update devops configs probably.
Here's the first stab at the vitejs refactor. I'm not completely done testing. When I start it up, I get the below screenshot with an error notification, `Could not set notifications.`, so I could have messed something up.
I also see `App.vue:346 Got vapid key:` in the browser console... which may just be an error in my local configuration.
To start the vite development server run:
```
npm run dev
```
The other big difference was having to change environment variables. Instead of `VUE_APP_`, the prefix is now `VITE_`.
**So, we'll need to update devops configs probably.**
Previous error:
Error: The following dependencies are imported but could not be resolved:
dexie-export-import/dist/import (imported by /Users/jason/dev/src/trent/crowd-funder-for-time-pwa/src/views/AccountViewView.vue?id=0)
Are they installed?
at file:///Users/jason/dev/src/trent/crowd-funder-for-time-pwa/node_modules/vite/dist/node/chunks/dep-DJaaTb_D.js:52506:23
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async file:///Users/jason/dev/src/trent/crowd-funder-for-time-pwa/node_modules/vite/dist/node/chunks/dep-DJaaTb_D.js:51972:38
Looks like the npm run serve doesn't work -- at least, I get a blank screen at the port it gives. Since npm run dev now runs fine, we can just remove the serve from the README.
I'll put items into separate comments.
- Looks like the `npm run serve` doesn't work -- at least, I get a blank screen at the port it gives. Since `npm run dev` now runs fine, we can just remove the `serve` from the README.
This one is a showstopper: on the account screen, "Download settings & contacts" gives a red error with this in the console: "Export Error: TypeError: (intermediate value).export is not a function", complaining about "generateDatabaseBlob"
This works OK on the other repo's master branch.
* This one is a showstopper: on the account screen, "Download settings & contacts" gives a red error with this in the console: "Export Error: TypeError: (intermediate value).export is not a function", complaining about "generateDatabaseBlob"
This works OK on the other repo's master branch.
Things work, but FYI with npm run dev when I make changes to files then the effects don't take place immediately -- which is curious because the console will show a message thus:
[vite] hot updated: /src/views/AccountViewView.vue
I only see changes when I reload.
Not a show-stopper.
Things work, but FYI with `npm run dev` when I make changes to files then the effects don't take place immediately -- which is curious because the console will show a message thus:
`[vite] hot updated: /src/views/AccountViewView.vue`
I only see changes when I reload.
Not a show-stopper.
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.
Here's the first stab at the vitejs refactor. I'm not completely done testing. When I start it up, I get the below screenshot with an error notification,
Could not set notifications., so I could have messed something up.I also see
App.vue:346 Got vapid key:in the browser console... which may just be an error in my local configuration.To start the vite development server run:
The other big difference was having to change environment variables. Instead of
VUE_APP_, the prefix is nowVITE_.So, we'll need to update devops configs probably.
Previous error: Error: The following dependencies are imported but could not be resolved: dexie-export-import/dist/import (imported by /Users/jason/dev/src/trent/crowd-funder-for-time-pwa/src/views/AccountViewView.vue?id=0) Are they installed? at file:///Users/jason/dev/src/trent/crowd-funder-for-time-pwa/node_modules/vite/dist/node/chunks/dep-DJaaTb_D.js:52506:23 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async file:///Users/jason/dev/src/trent/crowd-funder-for-time-pwa/node_modules/vite/dist/node/chunks/dep-DJaaTb_D.js:51972:38I'll put items into separate comments.
npm run servedoesn't work -- at least, I get a blank screen at the port it gives. Sincenpm run devnow runs fine, we can just remove theservefrom the README.This works OK on the other repo's master branch.
Things look pretty good! I think there's just that one issue. I'll try an actual deploy in docker onto the test server soon.
@@ -516,7 +516,6 @@<script lang="ts">import { AxiosError, AxiosRequestConfig } from "axios";import Dexie from "dexie";import "dexie-export-import";This is a line that is needed for the db.export call (since it adds to the Dexie prototype).
@@ -0,0 +12,4 @@alias: {"@": path.resolve(__dirname, "./src"),buffer: path.resolve(__dirname, 'node_modules', 'buffer'),'dexie-export-import/dist/import': 'dexie-export-import/dist/import/index.js',I now see this, which possibly takes the place of that import... so I guess we'll want to talk more about how this should work
It works to have both of these in place so I'll continue with both.
Okay. Sounds good @trentlarson
Things work, but FYI with
npm run devwhen I make changes to files then the effects don't take place immediately -- which is curious because the console will show a message thus:[vite] hot updated: /src/views/AccountViewView.vueI only see changes when I reload.
Not a show-stopper.
My work is continuing here: jsnbuchanan/crowd-funder-for-time-pwa#1