Fetch can not populate data anymore + Router + babel warnings on fresh instance

[mirkofisic]

New versions of nuxtjs really have huge problems:

1. In fetch method it is no longer possible to set/popualate any property within data is this big change or bug or I do something very wrong? I don't want to use the vuex store!

2. Babel warnings appear constantly in the console.
   Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties. The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding ["@babel/plugin-proposal-private-methods", { "loose": true }] to the "plugins" section of your Babel config.

3. A memory leak occurs very often on the router. At the moment, I can't reproduce the error on this project because where the memory leak appears I have a mongo database, so it's hard for me to share it.

4. If it is i18n is confugured in the nuxt-config:
   i18n: { detectBrowserLanguage: false, langDir: './locales', lazy: true, defaultLocale: 'en', strategy: 'prefix', },

if i use the locale function it never takes me into corect location/path, ecxample:
path: /en/manager
if I click some nuxt-link with the value of the training, application will change the url as:
/en/training
if currently path is:
path: /en/manager/
if I click some nuxt-link with the value of the training, application will change the url as:
/en/manager/training
how can I change the link that always start from the prefix?

Node Version: v12.18.4
Nuxtjs Version: package 2.15.3 but in console it prints version 2.15.4
project url: https://drive.google.com/file/d/1hh2oXqMbkPrd5QxHnkUCeMRXa-Pt1io2/view?usp=sharing

[danielroe]

I'm closing this group issue as it covers a lot of ground. (Next time, It's better to create separate issues for each thing you want to report, which makes it easier to respond and triage helpfully.)

However, for the points you've raised above:

1. I answered in your other issue Fetch can not set/populate data property #9318 (comment).
2. Fixed in fix(babel): loose option for babel class-properties and private-methods #9232
3. Please do open a new issue with a minimal reproduction (via https://template.nuxtjs.org) - and I'll look into it.
4. Please do open an issue at https://github.com/nuxt-community/i18n-module/ - we'd love to help.