WIP update vulnerable dependencies; update to vite#8
Conversation
rlassi
force-pushed
the
update-vulnerable-packages-plus-vue-vuetify-vite
branch
from
84f2f70 to
aca6a40
Compare
| export default defineConfig({ | ||
| plugins: [vue()], | ||
| resolve: { | ||
| alias: { |
There was a problem hiding this comment.
not sure if you are using an @ alias but it was part of the vite config setup steps so I figured I'd throw it in.
| alias: { | ||
| "@": path.resolve(__dirname, "./src"), | ||
| }, | ||
| extensions: [".mjs", ".js", ".ts", ".jsx", ".tsx", ".json", ".vue"], // allows importing files without adding file extension |
There was a problem hiding this comment.
According to vite this is actually not recommended. Vite recommends changing all vue sfc's (single file components) to have .vue extension on imports. ex - instead of import MyComponent from './MyComponent' you would need it to be import MyComponent from './MyComponent.vue'. However if the app is large and it would be a big ask to add the extension this is a work around. I didn't look into it, but there may be a migration tool that will rename imports accordingly...
| }, | ||
| }, | ||
| host: "127.0.0.1", | ||
| proxy: { "/": "http://localhost:8300" }, |
There was a problem hiding this comment.
I think this is where the openemr app is not connecting properly to the vue app and is causing the 503 codes from server. I can do some more debugging of this, but I figured I'd get your thoughts on it first.
There was a problem hiding this comment.
It looks like the dev server is starting on a different port now (not 8080) and the docker apache configuration has a reverse proxy to 8080. Is there a way to force vite to start devserver on 8080?
The apache conf is here (on the openemr Docker):
/etc/apache2/conf.d/openemr.conf
It might be helpful debugging the proxy to add these configs
proxy: {
'/' : {
target: "127.0.0.1:8300",
changeOrigin: true,
secure: false,
configure: (proxy, _options) => {
proxy.on('error', (err, _req, _res) => {
console.log('proxy error', err);
});
proxy.on('proxyReq', (proxyReq, req, _res) => {
console.log('Sending Request to the Target:', req.method, req.url);
});
proxy.on('proxyRes', (proxyRes, req, _res) => {
console.log('Received Response from the Target:', proxyRes.statusCode, req.url);
});
},
}
There was a problem hiding this comment.
That is a great idea. I'll add that in. I think I remember reading that there is a port key you can specify a custom port for the dev server. I'll check into it.
| @@ -1,3 +1,3 @@ | |||
| VUE_APP_BASE_URL=/openemr | |||
| VUE_APP_API_BASE_URL=/openemr | |||
There was a problem hiding this comment.
I'll remove these env changes from final commit before merging...
| import { newDashboard, newDataSourceColumn, newForm, newWorkspace } from './model-builder' | ||
|
|
||
| const baseUrl = process.env.VUE_APP_API_BASE_URL | ||
| const baseUrl = import.meta.VITE_API_BASE_URL |
There was a problem hiding this comment.
vite uses import.meta for env vars, and VITE_ instead of VUE_APP_ to signify client side env vars
2 participants
0 vulnerabilities found now with
npm audit. I think they were all resolved in the migration tovite. I don't havevueupdated to2.7yet orvuetifyupdated. In your slack message you mentioned bumpingvuetifyto2.6but it's already there. Did you want to bump it up further?Moving to
vitefromvue-cliis close. I can get the project up, but I am getting503errors from server and I think it has something to do with my proxy... or something else in thevite.config.jssetup. Can you take a look and see if you can resolve the issue?npm run devwill start the dev server. LMK if you have any questions or feedback.I referenced this for
vue-clitovitemigration - https://vueschool.io/articles/vuejs-tutorials/how-to-migrate-from-vue-cli-to-vite/