[Data Loaders] Reconcider addition of dataLoader/dataPageLoader SFC macros

[rijenkii]

unplugin-vue-router/docs/data-loaders/rfc.md

Lines 849 to 852 in ef056ab

	## Drawbacks
	- At first, it looks less intuitive than just awaiting something inside `setup()` with `<Suspense>` [but it doesn't have its limitations](#suspense) and have many more features
	- Requires an extra `<script>` tag but only for page components. A macro `definePageLoader()`/`defineLoader()` could be error-prone as it's very tempting to use reactive state declared within the component's `<script setup>` but that's not possible as the loader must be created outside of its `setup()` function

The requirement of using non-setup <script> to define pages with loaders is the only thing that turns me away from using data loaders in my projects.

Vanilla Vue already provides macros that accept local variables from <script setup>, hoists them and actively screams at the user if they did something egregiously wrong, so data loader macros could do the same:

<script setup lang="ts">
import { ref } from "vue";

const inheritProps = ref(true);
defineOptions({ inheritProps });
</script>

[vite:vue] [@vue/compiler-sfc] `defineOptions()` in <script setup> cannot reference locally declared variables because it will be hoisted outside of the setup() function. If your component options require initialization in the module scope, use a separate normal <script> to export the options instead.

/project/workspace/src/App.vue
3  |  
4  |  const inheritProps = ref(true);
5  |  defineOptions({ inheritProps });
   |                  ^^^^^^^^^^^^
6  |  </script>
7  |  

[posva]

I know 😅
Currently there is an experimental setting that automatically adds the export. I can’t remember the name, but it should be easy to find with auto completion on the experimental option

[rijenkii]

Thank you for the answer. Linked usage examples in the RFC comments to calm people down: vuejs/rfcs#460 (reply in thread)