This is so cool, hope it'll land on time for 2.13.x 👏

Codecov Report

Merging #7463 into dev will decrease coverage by 0.05%.
The diff coverage is 88.09%.

@@            Coverage Diff             @@
##              dev    #7463      +/-   ##
==========================================
- Coverage   70.28%   70.22%   -0.06%     
==========================================
  Files          88       88              
  Lines        3708     3714       +6     
  Branches     1011     1008       -3     
==========================================
+ Hits         2606     2608       +2     
- Misses        894      898       +4     
  Partials      208      208              

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2abbb99...5cf9634. Read the comment docs.

@pi0 Is there a measurable difference in parsing/loading server.js if not minimized? When you run a node server then that shouldn't matter much, but if you are using a lambda then that server.js could need to be parsed on almost every request.

@pimlie Agree however we are not currently officially supporting serverless target. Builders/Packers may utilize a minimizer to reduce size. I added build._minifyServer to make it easier until we improve support wdyt?

As long as its still configurable I am happy, thanks ;)

@pi0 Is there any way to disable this? My routes are deep and it seems with this change file urls get even deeper I think I am running into SplitChunksPlugin truncating filenames.

Here is my file tree:

pages/
├── current-item
│   ├── _n.vue
│   └── index.vue
├── current-item.vue
├── dashboards
│   ├── _dashboardId
│   │   ├── items
│   │   │   ├── _itemId
│   │   │   │   ├── details.vue
│   │   │   │   └── youritems
│   │   │   │       └── _youritemId.vue
│   │   │   ├── _itemId.vue
│   │   │   └── index.vue
│   │   └── index.vue
│   └── _dashboardId.vue
......

Examples of long urls that nuxt generated but have been truncated:

vendors.pages/current-vendors.pages/current-item/[_]n.pages/dashboards/[_]dashboardId/items/_itemId/youritems/_youritemId..4d40e1ae.142e679.js

vendors.pages/dashboards/[_]dashboardId/items/_itemId/details.pages/dashboards/[_]dashboardId/items/.9ad5534e.e5bd853.js

Nuxt is unable to load last url in the example, when I try to access it it responds with /* script not found */ message. If I however rename it from .9ad5534e.e5bd853.js to a.9ad5534e.e5bd853.js it is loadable.
I don't know why vendor.pages nest files that much deep. Maybe cyclic dependency thing?

What do you think?

Hi @OrkhanAlikhanov. It had to be fixed with #7603 but seems [_] is preserved. As a temporary fix you can use:

build: {
  filenames: { 
    chunk: '[contenthash:7].js'
  }
}

Thanks for the quick response. Actually #7603 made the bug apparent. Before it, the filename had _n.pages now it is [_]n.pages making it even longer and getting truncated. Thanks for the temporary solution.

I still wonder if that much nestedness is a bug or a feature. The url contains dashboards/[_]dashboardId/items/_itemId/details.pages/dashboards/[_]dashboardId/items/... but the if you look at the file tree, the file is dashboards/_dashboardId/items/details.vue, why does nuxt nest dashboards folder inside details.pages folder? How should we interpret that for the easy debugging in production?

@OrkhanAlikhanov Indeed it is not nice a file name when concatenation happens. Using [name] was meant to make tracing chunks easier but we may need a way to simplify it for this case.

I digged in the documention but dont see what the optimal setting for source mapping would be. I'm attaching a debugger to 9229 but I don't get any breakpoints to bind in neither VS debugger nor Chrome dev tools Node inspector ..