Mb for nuxt asyncData api, because waitFor not working for this
Something like this

export default function (waiter, func) {
  return async (...args) => {
    const { app } = args[0];

    try {
      app.wait.start(waiter);
      return await func.apply(this, args);
    } finally {
      app.wait.end(waiter);
    }
  };
};

Or if vue-wait have this function, sorry a

When scrolling we should check if the provided value dont exceeds the scroll limit. If we target value higer then maxScroll the easing effect is useless. If computed scroll value is more then browser maxscroll it should take maxscroll instead.

Version

v2.10.2

Reproduction link

https://github.com/nuxt-community/modules/blob/master/packages/browserconfig/index.js

Steps to reproduce

path.resolve(this.options.srcDir, 'static', browserconfigFileName) and `content: '/' + browserconfigFi

https://github.com/nuxt-community/auth-module/blob/85466345311bf882ae2f603ba43ef1dc638d2cdb/lib/core/auth.js#L58

The problem is with this line. It check whether current page enable auth middleware to see if you have right to stay on current page when logout. But I can't figure out the point of this check when login.

When I remove auth: false on page's option , or use auth: 'guest' the

What problem does this feature solve?

The @nuxtjs/firebase module provides service worker scripts for firebase auth sw sessions.

The problem is that (depending on where the script is included) it either:

• is ignored (because workbox responds with a caching strategy)
  or

What problem does this feature solve?

In the past, Brotli was not supported on nodejs servers.

If I understand correctly, this is now supported since a few months : nodejs/node#20458

This PR dropped support for Brotli : nuxt-community/axios-module#180

Maybe it's time to revert this BR because Axios is supporting it too : https://github.com/ax

Version

v6.7.0

Reproduction link

nuxt-community/nuxt-i18n#554

Steps to reproduce

Please add following tests:

expect(window.$nuxt.localePath('/about-us', 'fr')).toBe('/fr/a-propos')
expect(window.$nuxt.localePath({ path: '/about-us' }, 'fr')).

What problem does this feature solve?

how to use Apollo local state management? any examples? Let's say I want to create Apollo Local UI Cache State management. I our project we don't use vuex. as described in https://vue-apollo.netlify.com/guide/local-state.html#why-use-apollo-local-state-management

What problem does this feature solve?

Currently, if I want to use the @nuxtjs/router I'm left with a blank sitemap which doesn't take into account the custom routes I added manually in my router.js file as per @nuxtjs/router documentation. This would eliminate redundancy of definition of routes

What does the proposed changes look like?

Instead of using the result of createRoutes from

Version

1.4.1

Reproduction link

https://codesandbox.io/s/vue

Steps to reproduce

• Create a folder without an index.md, index.comp.md inside or a [foldername].comp.md, [foldername.md] at the same level

What is expected ?

Just to work without index or to display an informative error that ei

What problem does this feature solve?

In most places where dotenv is used system env vars override the dotenv vars, however dotenv-module does the exact opposite, swapping this around would give the expected result when using systemvars: true

Version

@nuxtjs/firebase: 5.0.7
@nuxtjs/pwa: 3.0.0-beta.20
firebase: 7.14.2
nuxt: 2.12.2

Reproduction Link

https://github.com/m2sd/nuxt-firebase-pwa-test

Steps to reproduce

Follow the steps in the repo

What is Expected?

Firebase ssr auth and Workbox should work in conjunction so that requests are augmented with authorization AND cached

What is actually happen

Is your feature request related to a problem? Please describe.
Some variables don't override if you import before like $grid-breakpoints and $display-breakpoints

I think is because the instance of $display-breakpoints and $grid-breakpoints was created before the override variables ..

For this reason, when you override $grid-breakpoints, the variables $display-breakpoints still was the v

What problem does this feature solve?

This will reduce the app bundle size and improve initial loading speeds.

What does the proposed changes look like?

Following the guide here https://docs.sentry.io/platforms/javascript/#lazy-loading-sentry it should be possible, though it looks like the sentry loader is not available via npm :/

Demo app doesn't work in IE11, guess same goes for IE9+
(as far as i understood you use css-variables and they are not supported by IE)

![image](https://user-images.githubuse

nuxt.config.js

module.exports = {
    ...
    gtm: {
      id: // how to access the variable NUXT_APP_GTM here
    },
    modules: [
      [
        'nuxt-env',
        {
          keys: [
            {
              key: 'NUXT_APP_GTM',
              default: 'GTM-XXXXXXX'
            },
          ]
        }
      ]
    ]
    ...
  }

is there a way to acces