You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying out Vite + Vike for the first time, integrating it in an existing project by following https://vike.dev/add, running the server as I went along to ensure stuff worked.
Before step 4, this lead to me chasing the following warning:
[vike][Warning] Update to the new V1 design to get rid of Vite's warning: The glob option "as" has been deprecated in favour of "query". See https://vike.dev/migration/v1-design for how to migrate.
The glob option "as" has been deprecated in favour of "query". Please update as: 'extractExportNames' to query: '?extractExportNames'.
After digging through the code, I eventually found out this was due to the config.pageConfigs list being empty, (because I hadn't done step 4 yet).
Maybe there is another heuristic that can be used to find pre-V1 configs, which doesn't also trigger on partly set-up/empty projects (which are otherwise following V1 design)?
Or if there isn't, something could be added to the warning, explaining that this also comes up if you haven't configured any pages yet.
The text was updated successfully, but these errors were encountered:
Indeed, the warning's heuristic is faulty and I'm actually aware of that. The old design is going to be removed very soon so this will resolve itself very soon (ETA Q1). Thus closing. Thank you for reaching out about this; let us know if you stumble upon other paper cuts like this.
Description
I'm trying out Vite + Vike for the first time, integrating it in an existing project by following https://vike.dev/add, running the server as I went along to ensure stuff worked.
Before step 4, this lead to me chasing the following warning:
After digging through the code, I eventually found out this was due to the
config.pageConfigs
list being empty, (because I hadn't done step 4 yet).Maybe there is another heuristic that can be used to find pre-V1 configs, which doesn't also trigger on partly set-up/empty projects (which are otherwise following V1 design)?
Or if there isn't, something could be added to the warning, explaining that this also comes up if you haven't configured any pages yet.
The text was updated successfully, but these errors were encountered: