Skip to content

Releases: smastrom/vue-global-loader

v0.9.9

03 May 18:59
67d7bdb
Compare
Choose a tag to compare

Release notes

Add vue-global-loader to optimizeDeps.include when installing Nuxt module.

v0.9.8

03 May 18:21
df516c5
Compare
Choose a tag to compare

Release notes

Add default value fallback to inject to prevent upstream Nuxt 3.11 misbehavior. Thanks @BayBreezy, #2

v0.9.7

15 Dec 12:15
7110ee3
Compare
Choose a tag to compare

Release notes

Reduced default spinners size from:

  • 140px to 110px on desktop
  • 110px to 80px on high-res mobile devies
  • 90px to 70px on low-res mobile devices

v0.9.6

10 Dec 15:45
Compare
Choose a tag to compare

Release notes

This is the first release of vue-global-loader. Check the README for usage, examples and anything else you would need.

Development notes

I released this package using a different approach than any other Vue package I published so far.

In short, I'm not compiling the .vue files to .js files anymore. Reasons:

  • CSS. It's getting annoying requiring users to import .css files in their app entrypoint. Vue components already have a <style> tag and it would be great if also package consumers start benefiting from it, not just first-party components.
  • Vue-compiler versions. From Vue docs it's not clear which Vue version range users should use according to the compiler version used to bundle the package. When I'm in charge of the compilation, I can't be sure that it will work with any minor version of Vue neither I can lose time testing it against all of them. This package is written in a syntax supported by Vue 3.0.0 hence it should work with any Vue version >= 3.0.0. Compilation is up to the package consumer which will get the matching output / benefits according to its Vue version.
  • Nuxt modules. To fully leverage Nuxt features, components should be added to the app by the modules as .vue files and let Nuxt handle the rest. JS components cannot also be prefixed with Lazy nor can be debugged easily. This is now done as expected.
  • Hard debugging. When investigating edge cases is practically impossible to enter the node_modules folder and debug the components directly. This is now possible for both the maintainer and the package consumer.
  • No more JS minification. Same reason as above.

The only downside is that this package won't work in setups that don't require a build step.