text:
Webpack and Dependency Error on Nuxt and Nuxt generate commands

CMTY hangs and never submits, copy and pasted preview. Please open.

Version
v2.6.3
Reproduction link
https://github.com/khrome83/culturescreen.io
Steps to reproduce
Clone Repo, run nuxt or nuxt generate
What is expected ?
Expect nuxt and nuxt generate to run correctly.
What is actually happening?
Errors from running nuxt

 WARN  Compiled with 28 warnings                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Critical dependency: require function is used in a way in which dependencies cannot be statically extracted                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/express/lib/view.js                                                                                friendly-errors 06:57:33

Critical dependency: the request of a dependency is an expression                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'arc-templates/dist/es5' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'dust' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'dustjs-helpers' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/hard-source-webpack-plugin/lib/SupportExtractTextPlugin.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'extract-text-webpack-plugin' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/hard-source-webpack-plugin/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in (webpack)/lib/debug/ProfilingPlugin.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'inspector' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/webpack/lib/debug'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/esm/esm.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'internal/bootstrap/loaders' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/esm'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'jade' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'liquid-node' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'node-gyp' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/fsevents/node_modules/node-pre-gyp/lib/util'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'npm' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/fsevents/node_modules/node-pre-gyp/lib/util'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'nunjucks' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'pug' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'qejs' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'swig' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'swig-templates' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'then-jade' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'then-pug' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'tinyliquid' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/consolidate/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/hard-source-webpack-plugin/lib/ParallelModulePlugin.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'webpack-cli' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/hard-source-webpack-plugin/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/hard-source-webpack-plugin/lib/ParallelModulePlugin.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'webpack-command' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/hard-source-webpack-plugin/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/hard-source-webpack-plugin/lib/TransformGeneratorPlugin.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'webpack/lib/WebAssemblyGenerator' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/hard-source-webpack-plugin/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/hard-source-webpack-plugin/lib/TransformParserPlugin.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'webpack/lib/WebAssemblyParser' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/hard-source-webpack-plugin/lib'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/write-file-atomic/index.js                                                                                friendly-errors 06:57:33

Module not found: Error: Can't resolve 'worker_threads' in '/Users/zane/GitHub/culturescreen.io/www/node_modules/write-file-atomic'                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/fsevents/node_modules/node-pre-gyp/lib/util/nw-pre-gyp/index.html                                                                                friendly-errors 06:57:33

Module parse failed: Unexpected token (1:0)                                                                                friendly-errors 06:57:33
You may need an appropriate loader to handle this file type.
> <!doctype html>
| <html>
| <head>
                                                                                friendly-errors 06:57:33
 @ ./node_modules/fsevents/node_modules/node-pre-gyp/lib sync ^\.\/.*$
 @ ./node_modules/fsevents/node_modules/node-pre-gyp/lib/node-pre-gyp.js
 @ ./node_modules/fsevents/fsevents.js
 @ ./node_modules/chokidar/lib/fsevents-handler.js
 @ ./node_modules/chokidar/index.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true&timeout=30000&ansiColors=&overlayStyles=&name=client&path=/__webpack_hmr/client ./.nuxt/client.js
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/loader-runner/lib/loadLoader.js                                                                                friendly-errors 06:57:33

System.import() is deprecated and will be removed soon. Use import() instead.                                                                                friendly-errors 06:57:33
For more info visit https://webpack.js.org/guides/code-splitting/
                                                                                friendly-errors 06:57:33
 @ ./node_modules/loader-runner/lib/LoaderRunner.js 7:17-40
 @ (webpack)/lib/NormalModule.js
 @ (webpack)/lib/AutomaticPrefetchPlugin.js
 @ (webpack)/lib/webpack.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true&timeout=30000&ansiColors=&overlayStyles=&name=client&path=/__webpack_hmr/client ./.nuxt/client.js
                                                                                friendly-errors 06:57:33

 WARN  in ./node_modules/@vue/component-compiler-utils/node_modules/prettier/parser-glimmer.js                                                                                friendly-errors 06:57:33

require.extensions is not supported by webpack. Use a loader instead.                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33
 @ ./node_modules/@vue/component-compiler-utils/node_modules/prettier/index.js 35684:13-40
 @ ./node_modules/@vue/component-compiler-utils/dist/compileTemplate.js
 @ ./node_modules/@vue/component-compiler-utils/dist/index.js
 @ ./node_modules/vue-loader/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true&timeout=30000&ansiColors=&overlayStyles=&name=client&path=/__webpack_hmr/client ./.nuxt/client.js
                                                                                friendly-errors 06:57:33

 ERROR  Failed to compile with 139 errors                                                                                friendly-errors 06:57:33

These dependencies were not found:                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33
* atpl in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* aws-sdk in ./node_modules/fsevents/node_modules/node-pre-gyp/lib/publish.js                                                                                friendly-errors 06:57:33
* bracket-template in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* child_process in ./node_modules/fsevents/node_modules/detect-libc/lib/detect-libc.js, ./node_modules/fsevents/node_modules/node-pre-gyp/lib/testbinary.js and 7 others                                                                                friendly-errors 06:57:33
* coffee-script in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* core-js/modules/es7.promise.finally in ./.nuxt/client.js                                                                                friendly-errors 06:57:33
* dot in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* dustjs-linkedin in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* eco in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* ect in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* fs in ./node_modules/@nuxt/config/dist/config.js, ./node_modules/@nuxt/core/dist/core.js and 73 others                                                                                friendly-errors 06:57:33
* haml-coffee in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* hamlet in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* hamljs in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* hogan.js in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* htmling in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* jazz in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* jqtpl in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* jsdom in ./node_modules/@nuxt/server/dist/server.js                                                                                friendly-errors 06:57:33
* just in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* less in ./node_modules/@vue/component-compiler-utils/dist/styleProcessors/index.js                                                                                friendly-errors 06:57:33
* level in ./node_modules/hard-source-webpack-plugin/lib/SerializerLeveldb.js                                                                                friendly-errors 06:57:33
* liquor in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* marko in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* module in ./node_modules/@nuxt/core/dist/core.js, ./node_modules/@vue/component-compiler-utils/node_modules/prettier/third-party.js and 8 others                                                                                friendly-errors 06:57:33
* mote in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* net in ./node_modules/express/lib/request.js, /Users/zane/node_modules/babel-core/node_modules/debug/src/node.js and 3 others                                                                                friendly-errors 06:57:33
* node-sass in ./node_modules/@vue/component-compiler-utils/dist/styleProcessors/index.js                                                                                friendly-errors 06:57:33
* plates in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* ractive in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* readline in ./node_modules/@nuxt/friendly-errors-webpack-plugin/src/utils/log.js                                                                                friendly-errors 06:57:33
* slm in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* stylus in ./node_modules/@vue/component-compiler-utils/dist/styleProcessors/index.js                                                                                friendly-errors 06:57:33
* teacup/lib/express in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* templayed in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* tls in /Users/zane/node_modules/forever-agent/index.js, /Users/zane/node_modules/tunnel-agent/index.js                                                                                friendly-errors 06:57:33
* toffee in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* twig in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* underscore in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* vash in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* velocityjs in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* walrus in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
* whiskers in ./node_modules/consolidate/lib/consolidate.js                                                                                friendly-errors 06:57:33
                                                                                friendly-errors 06:57:33
To install them, you can run: npm install --save atpl aws-sdk bracket-template child_process coffee-script core-js/modules/es7.promise.finally dot dustjs-linkedin eco ect fs haml-coffee hamlet hamljs hogan.js htmling jazz jqtpl jsdom just less level liquor marko module mote net node-sass plates ractive readline slm stylus teacup/lib/express templayed tls toffee twig underscore vash velocityjs walrus whiskers

Errors from running nuxt generate
> culturescreen.io.www@2.6.3 now-build /tmp/2b68b5e0/www
> nuxt generate
BUILD    Apr 30 2019 06:58:15:266    ...package.json
11:58:15 ℹ Production build
BUILD    Apr 30 2019 06:58:15:374    ...package.json
11:58:15 ✔ Builder initialized
BUILD    Apr 30 2019 06:58:15:406    ...package.json
11:58:15 ✔ Nuxt files generated
BUILD    Apr 30 2019 06:58:17:340    ...package.json
webpackbar 11:58:17 ℹ Compiling Client
BUILD    Apr 30 2019 06:58:17:350    ...package.json
11:58:17 ℹ Starting type checking service...
BUILD    Apr 30 2019 06:58:17:350    ...package.json
11:58:17 ℹ Using 1 worker with 2048MB memory limit
BUILD    Apr 30 2019 06:58:54:710    ...package.json
webpackbar 11:58:54 ✔ Client: Compiled with some errors in 37.37s
BUILD    Apr 30 2019 06:58:54:725    ...package.json

Hash: b613876c5d95ac22720c
Version: webpack 4.30.0
Time: 37370ms
Built at: 2019-04-30 11:58:54
                  Asset      Size  Chunks  Chunk Names
16f9e326e4dbd4885223.js  22.4 MiB       8  vendors.pages/index
2578f495ea3cdae1a85e.js  27.3 KiB       5  pages/index
5fd12d129fa57e0c7ac7.js   593 KiB       3  commons.pages/index
7a44ffa366123dd30910.js   393 KiB       7  vendors.app
8f6965724c5ecff2a353.js   411 KiB       1  app
               LICENSES  4.35 KiB
a00a0fc023a78964f5ba.js  19.9 KiB       0  vendors.pages/feed.pages/index
a4569709afc926028503.js  2.32 KiB       6  runtime
ac245d8c70b6614fcf6e.js   158 KiB       2  commons.app
babd6f4439793bb46b4e.js  4.02 KiB       4  pages/feed
        img/d98f2c8.svg  15.9 KiB
Entrypoint app = a4569709afc926028503.js ac245d8c70b6614fcf6e.js 7a44ffa366123dd30910.js 8f6965724c5ecff2a353.js

WARNING in ./node_modules/terser-webpack-plugin/dist/worker.js 12:130-137
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
 @ ./node_modules/terser-webpack-plugin/dist/TaskRunner.js
 @ ./node_modules/terser-webpack-plugin/dist/index.js
 @ ./node_modules/terser-webpack-plugin/dist/cjs.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

WARNING in ./node_modules/consolidate/lib/consolidate.js 1667:13-20
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
 @ ./node_modules/consolidate/index.js
 @ ./node_modules/@vue/component-compiler-utils/dist/compileTemplate.js
 @ ./node_modules/@vue/component-compiler-utils/dist/index.js
 @ ./node_modules/vue-loader/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

WARNING in ./node_modules/esm/esm.js 1:761-768
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
 @ ./node_modules/@nuxt/co
BUILD    Apr 30 2019 06:58:54:725    ...package.json
js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

WARNING in ./node_modules/consolidate/lib/consolidate.js 1421:9-27
require.extensions is not supported by webpack. Use a loader instead.
 @ ./node_modules/consolidate/index.js 1:17-45
 @ ./node_modules/@vue/component-compiler-utils/dist/compileTemplate.js
 @ ./node_modules/@vue/component-compiler-utils/dist/index.js
 @ ./node_modules/vue-loader/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

WARNING in ./node_modules/ejs/lib/ejs.js 904:2-20
require.extensions is not supported by webpack. Use a loader instead.
 @ (webpack)-bundle-analyzer/lib/viewer.js 19:12-26 66:22-36
 @ (webpack)-bundle-analyzer/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

WARNING in ./node_modules/ejs/lib/ejs.js 903:4-22
require.extensions is not supported by webpack. Use a loader instead.
 @ (webpack)-bundle-analyzer/lib/viewer.js 19:12-26 66:22-36
 @ (webpack)-bundle-analyzer/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

WARNING in ./node_modules/consolidate/lib/consolidate.js 1418:6-24
require.extensions is not supported by webpack. Use a loader instead.
 @ ./node_modules/consolidate/index.js 1:17-45
 @ ./node_modules/@vue/component-compiler-utils/dist/compileTemplate.js
 @ ./node_modules/@vue/component-compiler-utils/dist/index.js
 @ ./node_modules/vue-loader/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=t
BUILD    Apr 30 2019 06:58:54:725    ...package.json
ue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

ERROR in ./node_modules/graceful-fs/graceful-fs.js
Module not found: Error: Can't resolve 'fs' in '/tmp/2b68b5e0/www/node_modules/graceful-fs'
 @ ./node_modules/graceful-fs/graceful-fs.js 1:9-22
 @ ./node_modules/fs-extra/lib/fs/index.js
 @ ./node_modules/fs-extra/lib/index.js
 @ ./node_modules/@nuxt/core/dist/core.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

ERROR in ./node_modules/gzip-size/index.js
Module not found: Error: Can't resolve 'fs' in '/tmp/2b68b5e0/www/node_modules/gzip-size'
 @ ./node_modules/gzip-size/index.js 2:11-24
 @ (webpack)-bundle-analyzer/lib/tree/Folder.js
 @ (webpack)-bundle-analyzer/lib/analyzer.js
 @ (webpack)-bundle-analyzer/lib/viewer.js
 @ (webpack)-bundle-analyzer/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

ERROR in ./node_modules/html-webpack-plugin/index.js
Module not found: Error: Can't resolve 'fs' in '/tmp/2b68b5e0/www/node_modules/html-webpack-plugin'
 @ ./node_modules/html-webpack-plugin/index.js 7:11-24
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

ERROR in ./node_modules/html-webpack-plugin/node_modules/uglify-js/tools/node.js
Module not found: Error: Can't resolve 'fs' in '/tmp/2b68b5e0/www/node_modules/html-webpack-plugin/node_modules/uglify-js/tools'
 @ ./node_modules/html-webpack-plugin/node_modules/uglify-js/tools/node.js 1:9-22
 @ ./node_modules/html-webpack-plugin/node_modules/html-minifier/src/htmlminifier.js
 @ ./node_modules/html-webpack-plugin/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/Th
BUILD    Apr 30 2019 06:58:54:725    ...package.json
de_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

ERROR in ./node_modules/consolidate/lib/consolidate.js
Module not found: Error: Can't resolve 'plates' in '/tmp/2b68b5e0/www/node_modules/consolidate/lib'
 @ ./node_modules/consolidate/lib/consolidate.js 1402:55-72
 @ ./node_modules/consolidate/index.js
 @ ./node_modules/@vue/component-compiler-utils/dist/compileTemplate.js
 @ ./node_modules/@vue/component-compiler-utils/dist/index.js
 @ ./node_modules/vue-loader/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

ERROR in ./node_modules/consolidate/lib/consolidate.js
Module not found: Error: Can't resolve 'ractive' in '/tmp/2b68b5e0/www/node_modules/consolidate/lib'
 @ ./node_modules/consolidate/lib/consolidate.js 1218:57-75
 @ ./node_modules/consolidate/index.js
 @ ./node_modules/@vue/component-compiler-utils/dist/compileTemplate.js
 @ ./node_modules/@vue/component-compiler-utils/dist/index.js
 @ ./node_modules/vue-loader/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

ERROR in ./node_modules/consolidate/lib/consolidate.js
Module not found: Error: Can't resolve 'react' in '/tmp/2b68b5e0/www/node_modules/consolidate/lib'
 @ ./node_modules/consolidate/lib/consolidate.js 1438:54-70
 @ ./node_modules/consolidate/index.js
 @ ./node_modules/@vue/component-compiler-utils/dist/compileTemplate.js
 @ ./node_modules/@vue/component-compiler-utils/dist/index.js
 @ ./node_modules/vue-loader/lib/index.js
 @ ./node_modules/@nuxt/webpack/dist/webpack.js
 @ ./node_modules/@nuxt/builder/dist/builder.js
 @ ./node_modules/nuxt/dist/nuxt.js
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue?vue&type=script&lang=ts&
 @ ./components/TheFooter.vue
 @ ./node_modules/babel-loader/lib??ref--3-0!./node_modules/ts-loader??ref--3-1!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue?vue&type=script&lang=ts&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./
BUILD    Apr 30 2019 06:58:54:733    ...package.json

11:58:54  FATAL  Nuxt Build Error

  at WebpackBundler.webpackCompile (node_modules/@nuxt/webpack/dist/webpack.js:5379:13)
  at <anonymous>
  at process._tickDomainCallback (internal/process/next_tick.js:228:7)
BUILD    Apr 30 2019 06:58:54:793    ...package.json

   ╭─────────────────────────────╮
   │                             │
   │   ✖ Nuxt Fatal Error        │
   │                             │
   │   Error: Nuxt Build Error   │
   │                             │
   ╰─────────────────────────────╯
BUILD    Apr 30 2019 06:58:54:834    ...package.json
npm
BUILD    Apr 30 2019 06:58:54:835    ...package.json
 ERR! code ELIFECYCLE
npm ERR! errno 1
BUILD    Apr 30 2019 06:58:54:835    ...package.json
npm
BUILD    Apr 30 2019 06:58:54:835    ...package.json
 ERR! culturescreen.io.www@2.6.3 now-build: `nuxt generate`
npm ERR!
BUILD    Apr 30 2019 06:58:54:835    ...package.json
 Exit status 1
BUILD    Apr 30 2019 06:58:54:835    ...package.json
npm ERR!
npm
BUILD    Apr 30 2019 06:58:54:835    ...package.json
ERR! Failed at the culturescreen.io.www@2.6.3 now-build script.
npm ERR!
BUILD    Apr 30 2019 06:58:54:836    ...package.json
 This is probably not a problem with npm. There is likely additional logging output above.
BUILD    Apr 30 2019 06:58:54:842    ...package.json
npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/.npm/_logs/2019-04-30T11_58_54_836Z-debug.log
BUILD    Apr 30 2019 06:58:54:846    ...package.json
Error: Exited with 1
    at ChildProcess.child.on (/tmp/utils/node_modules/@now/build-utils/dist/fs/run-user-scripts.js:28:24)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

hello, are you ok?

I believe the issue was related to imports. The error message was not helpful in this case. But I am not 100% sure. I rebuilt everything a dozen times until it started to work.

Got this problem here too! Did you find a solution? Thanks! 🍻

It happened to me just now when I imported from nuxt package inside an error layout. Feels like a recursive error.


text:
SyntaxError : Unexpected identifier with a blank new project.

Hi there!
Since Nuxt 2.8.0, when i create a new project, if i create it without dependencies, everythin goes fine. But, when i added some dependencies (like Axios, or Bootstrap) the error appears since the first 'npm run dev' execution.

This question is available on Nuxt community (#c9293)

Hi. Related to a known issue (#5822). Next release of BootstrapVue is in few hours.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
avoid redirect loops

Reference: https://github.com/nuxt/framework/pull/3908#issuecomment-1079665687
With redirectTo, it is possible to make a loop condition return navigateTo(to.path).
A simple fix would be check and avoid redirect to exact same URL.
In more complex cases, a redirect loop can be nested like a~>b~>a which we could implement with help of a persisted state. (we can wait for this until having session support and benefit from session to hold such state)

Having discussed as a team, we think we could implement the following when there are too many redirections:

a more verbose warning in dev mode on client
a server-error (ERR_TOO_MANY_REDIRECTS)

see also https://github.com/vuejs/router/commit/e3dcc8d9477e17f9b92e22.
There may also be a further similar upstream issue in nitro that is separate from Nuxt that we can track in the nitro repository instead of here.

repo: nuxt/nuxt


text:
[Docs] Obsolete documentation-text regarding target static

https://v3.nuxtjs.org/api/configuration/nuxt.config#ssr has the following text:

Whether to enable rendering of HTML - either dynamically (in server mode) or at generate time. If set to false and combined with static target, generated pages will simply display a loading screen with no content.

I believe this is obsolete, because there is no static target option anymore.

How does one enable static in nuxt 3 without that option?

@Sharif-SS

How does one enable static in nuxt 3 without that option?

You simply call nuxi generate.
It will prerender all routes into HTML files suitable for static hosting. This is in contrast to nuxi build, which builds a server-application suitable for hosting via node.js.

@Sharif-SS

How does one enable static in nuxt 3 without that option?

You simply call nuxi generate.
It will prerender all routes into HTML files suitable for static hosting. This is in contrast to nuxi build, which builds a server-application suitable for hosting via node.js.

So lets say I change this to

nuxi generate instead, I should get netlify to generate the static version instead?

@danielroe I just noticed that the documentation on the website is still showing the old text.
See https://nuxt.com/docs/api/configuration/nuxt-config#ssr

Thanks for the ping. Indeed, it was hard coded to v3.1.0 documentation 🤦

authors: Sharif-SS aa-ndrej codeflorist danielroe


text:
Css styles from UnoCss @apply are missing in production bundle when cssnano is active

Environment

Operating System: Windows_NT
Node Version:     v18.14.0
Nuxt Version:     3.2.2
Nitro Version:    2.2.2
Package Manager:  pnpm@7.27.0
Builder:          vite
User Config:      experimental, modules, unocss, css
Runtime Modules:  @unocss/nuxt@0.49.7
Build Modules:    -

Reproduction
Note: Error happens only on production build.
https://stackblitz.com/edit/github-gxjzue?file=app.vue
Describe the bug
With @apply the styles are working fine in the Nuxt development server. But in the production bundle some styles are missing depending on the order.
Disabling cssnano in nuxt.config.ts would resolve the error.
Additional context
.text1 {
  @apply bg-slate-200;
  @apply text-center;
}
.test2 {
  @apply text-center;
  @apply bg-slate-200;
}

Resulting bundle:
.test1{--un-bg-opacity:1;background-color:rgba(226,232,240,var(--un-bg-opacity));text-align:center}
.test2{--un-bg-opacity:1;background-color:rgba(226,232,240,var(--un-bg-opacity))}    /* MISSING text-align:center */

Logs
No response

Resolved with https://github.com/unocss/unocss/pull/2229


text:
Hydration mismatch warning when using a rich-text renderer

Environment
Nuxt project info:

Operating System: Linux
Node Version:     v16.17.0
Nuxt Version:     3.2.2
Nitro Version:    2.2.2
Package Manager:  pnpm@7.1.0
Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://codesandbox.io/p/sandbox/dreamy-mcclintock-3j327f
Describe the bug
Using a rich-text renderer causes an hydration mismatch in nuxt3. It did not happen in nuxt2.
Looking at the source code of the library, shows that it does nothing special, just renders a series of elements. But the output that the server throws is a mismatch with the one that the client throws. Seems like the server only renders the first child?
Do you have any hints to what I should investigate?
Additional context
No response
Logs
Vue warn]: Hydration text mismatch:
- Client: "When we launched in 2006, our ambition was simple: help businesses grow. We started with payments, taking an engineering-first approach to solving some of the most complex challenges. Today, we are the preferred financial technology platform of many of the world's leading brands. We did this by working with exceptional talent, prioritizing success over ego, and having fun along the way."
- Server: "When we launched in 2006, our ambition was simple: help businesses grow. We started with payments, taking an engineering-first approach to solving some of the most complex challenges. "
  at <RichText document= Objectcontent: Array(2)0: {data: {…}, content: Array(6), nodeType: 'paragraph'}content: (6) [{…}, {…}, {…}, {…}, {…}, {…}]data: {}nodeType: "paragraph"[[Prototype]]: Object1: {data: {…}, content: Array(1), nodeType: 'paragraph'}length: 2[[Prototype]]: Array(0)data: {}nodeType: "document"[[Prototype]]: Object >
  at <RichText>
  at <App key=2 >
  at <NuxtRoot>
warn2 @ chunk-Q53DPCWL.js:1381

It seems there is a mismatch 🤔
Server result:

When we launched in 2006, our ambition was simple: help businesses grow. We started with payments, taking an
          engineering-first approach to solving some of the most complex challenges. Today, we are the preferred
          financial technology platform of many of the world's leading brands. We did this by working with
          exceptional talent, prioritizing success over ego, and having fun along the way.

To continue driving towards our long-term ambitions, we’re looking for innovative problem solvers, strategic
          thinkers, and colleagues we can count on.

Client:

When we launched in 2006, our ambition was simple: help businesses grow. We started with payments, taking an
          engineering-first approach to solving some of the most complex challenges. Today, we are the preferred
          financial technology platform of many of the world's leading brands. We did this by working with
          exceptional talent, prioritizing success over ego, and having fun along the way.

To continue driving towards our long-term ambitions, we’re looking for innovative problem solvers, strategic
          thinkers, and colleagues we can count on.

          ```

(On the train so only limited debugging capabilities due to wifi)

Hmmm, I cannot pinpoint what could cause the mismatch as it is the same data. And same code executed.
In your example I see the the world's vs  the world's, although in the warning message it seemed like it was missing a whole block:

Client: "When we launched in 2006, our ambition was simple: help businesses grow. We started with payments, taking an engineering-first approach to solving some of the most complex challenges. Today, we are the preferred financial technology platform of many of the world's leading brands. We did this by working with exceptional talent, prioritizing success over ego, and having fun along the way."

Server: "When we launched in 2006, our ambition was simple: help businesses grow. We started with payments, taking an engineering-first approach to solving some of the most complex challenges. "

Only reason that I can think, is that now it uses import { h } from 'vue' instead of the createElement function that was passed before.

Neither of these is a Nuxt issue, from what I can tell. Check if you can reproduce with https://stackblitz.com/github/nuxt-contrib/vue3-ssr-starter. This may be a difference with how Vue 3 handles whitespace.

@danielroe Correct, it does also throw the error in the vue3-ssr-starter https://stackblitz.com/edit/github-6za3kr?file=src%2Fpages%2FHome.vue
Where should I report it?

Thanks for opening that issue. ❤ I'm going to close it here as it's not an issue with Nuxt.

I am not sure its same issue but I think but when we use textarea to save text it throw same mismatch issue
here is example can be reproduce

 Some text without any new line or spaces

works find but when we do

 Some text with new line and space
 Some text with new line and space

Some text with new line and space
Some text with new line and space

Some text with new line and space

Now it throw error hydration mismatch issue

authors: MuhammadKhizar7 danielroe manniL willylatorre


text:
Has the official staff tried to download nuxt3 from the official website and use npm run build to package the file and then send pictures or word, ppt and other types of files exceeding 10kb?

Environment
node 18.16.0
nuxt  3.6.3
nuxi 3.6.3
nitro 2.5.2
Reproduction
无
Describe the bug
Why not try to download an initial project package from nuxt3 official website, and then configure an element-plus plug-in in it, and create a file sending function with plus, and open the project with npm run dev. However, the use of npm run build can not exceed 10kb pictures or non-TXT files, in which many experiments, you can even find that this error will appear before the api request, meaning that any api interface can appear this error, do not need the real api interface. Looking for a long time, finally found the nuxt3 itself left behind the problem, but I think I am not qualified to move the nuxt3 source code, I have not the ability. I wish the people developing the nuxt3 framework would pay attention to this problem
Additional context
No response
Logs
[nuxt] [request error] [unhandled] [500] fetch failed (url)
  at async sendProxy (/C:/Users/ASUS/Desktop/SRRNuxt/newNuxt3/.output/server/node_modules/h3/dist/index.mjs:521:20)
  at async Object.handler (/C:/Users/ASUS/Desktop/SRRNuxt/newNuxt3/.output/server/node_modules/h3/dist/index.mjs:1284:19)
  at async Server.toNodeHandle (/C:/Users/ASUS/Desktop/SRRNuxt/newNuxt3/.output/server/node_modules/h3/dist/index.mjs:1359:7)
[nuxt] [request error] [unhandled] [500] fetch failed (url)
  at async sendProxy (/C:/Users/ASUS/Desktop/SRRNuxt/newNuxt3/.output/server/node_modules/h3/dist/index.mjs:521:20)
  at async Object.handler (/C:/Users/ASUS/Desktop/SRRNuxt/newNuxt3/.output/server/node_modules/h3/dist/index.mjs:1284:19)
  at async Server.toNodeHandle (/C:/Users/ASUS/Desktop/SRRNuxt/newNuxt3/.output/server/node_modules/h3/dist/index.mjs:1359:7)

let's track in your first issue: https://github.com/nuxt/nuxt/issues/21936


text:
Wrong types instead of union when fetching API routes having dynamic and static handler

Environment

Operating System: Darwin
Node Version:     v18.16.1
Nuxt Version:     3.6.5
Nitro Version:    2.5.2
Package Manager:  pnpm@8.5.0
Builder:          vite
User Config:      devtools, nitro, runtimeConfig
Runtime Modules:  -
Build Modules:    -

Reproduction
Important: Run it locally as StackBlitz limited TS support (for Vue files especially).
https://stackblitz.com/edit/nuxt-22488?file=app.vue,README.md
Manual repro:

Create /server/api/posts/[id].get.ts and return anything, e.g. export default defineEventHandler(async () => 42)
Create /server/api/posts/static.get.ts and return some thing different, e.g. export default defineEventHandler(async () => 'static')
Change your app.vue to the following and see the TypeScript "test types" failing, as data is not 42 | 'static' nor number | string but unknown.

<script lang="ts" setup>
import type { Ref } from 'vue';

const getId = () => 'random';
const id = getId();

const { data } = await useFetch(`/api/posts/` + id);
//       ^?

export type Equals<X, Y> = (<T>() => T extends X ? 1 : 2) extends <T>() => T extends Y ? 1 : 2
  ? true
  : false;

export type Expect<T extends true> = T;
export type ExpectNot<T extends false> = T;

type _TEST = [
  ExpectNot<Equals<typeof data, Ref<unknown>>>,
  ExpectNot<Equals<typeof data, Ref<any>>>
];
</script>

<template>
  <div>
    {{ data }}
  </div>
</template>

Describe the bug
When having API routes that are targeting the same URL, for example /api/posts/[id].get.ts and /api/posts/static.get.ts the types of their return values are not inferred correctly when using $fetch or useFetch. Instead, unknown will be returned (or any when not using strict mode).

What should be returned is a union of possible types.
Additional context
In Nitro, this works as expected
(Also suggested to run locally to check)

Logs
No response

I think you need to do /api/posts/${id} and not /api/posts/ + id or TS can't use string literal inference.

I think you need to do /api/posts/${id} and not /api/posts/ + id or TS can't use string literal inference.

That's what I tried initially 😋
Unfortunately with the same result

Ah, okay. (Didn't test locally.)

I have also tried this and it seems to not infer the types from api routes, I have tried all the examples in the serialization section of the Nuxt docs and none of them seem to infer types from the api using useFetch or $fetch
Also I cannot get the superjson example to work without setting the response header to
event.node.res.setHeader("Content-Type", "text/plain");
Using Version: Nuxt 3.7.2 with Nitro 2.6.3

Is there a temporary workaround for this until a fix comes?

For anyone reading this, a dirty workaround for this is:
On the client:
const { data } = await useFetch(`/api/project/:${id}`)

notice the : before the ${id} That should properly give you the correct return type.
In the api endpoint, you then have to do:
export default defineEventHandler(async (event) => {
  const id = getRouterParam(event, 'id')?.split(':')[1]!

  // ...
}

Millage may vary without proper validation, but it works.

notice the : before the ${id} That should properly give you the correct return type.

Have to try this, but if this works, then maybe getRouterParam should remove leading : by default.

authors: danielroe genu manniL mubaidr shaun-fitzgibbon


text:
Cannot import from core-js/es/<feature>, but can from core-js/actual/<feature>

Environment
Happening on my machine in the project that uses nuxt v3.12.4, reproducible on StackBlitz on v3.14.x
- Operating System: Windows_NT
- Node Version:     v18.20.3
- Nuxt Version:     3.12.4
- CLI Version:      3.12.0
- Nitro Version:    2.9.7
- Package Manager:  npm@10.7.0
- Builder:          -
- User Config:      -
- Runtime Modules:  -
- Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-gb9b9p?file=plugins%2Fpolyfills.ts
In comparison, plain Vue+Vite doesn't complain about the same import:
https://stackblitz.com/edit/vitejs-vite-mcmudf?file=src%2Fmain.js
Describe the bug
I was trying to add some polyfills from core-js in a fake Nuxt plugin (see plugins/polyfills.ts in the reproduction) - by the way, is this the right way of doing that?
When I import from core-js/es like that
import 'core-js/es/array/to-spliced'; // ❌

I'm getting the following error in the console, and 500 error in the app:
 ERROR  [nuxt] [request error] [unhandled] [500] Cannot find module '../../modules/es.array.to-spliced'
Require stack:
- /home/projects/nuxt-starter-gb9b9p/core-js/es/array/to-spliced

If I change es to actual, the error would go away:
import 'core-js/actual/array/to-spliced'; // ✅

Additional context
No response
Logs

Would you see if you can reproduce this in pure Nitro (reproduction sandbox), and if so, raise there? 🙏


text:
[Table] New generic slots.

Description
Currently, we have slots named <column>-header and <column>-data. However, in some scenarios, it may be necessary to intercept all cells, regardless of the column name.
It would be beneficial to introduce generic header and data slots.
<UTable>
  <template #data="{ row }">
    Now, all data cells are equal.
  </template>
</UTable>

Additional context
No response

I'm also looking for a way to manipulate the header because I would like to display icons there

I'm also looking for a way to manipulate the header because I would like to display icons there

@migro1982 you can do something like this.
It's not as obvious as proposed in the issue, but it solves the problem.
<template
  v-for="header in headers"
  :key="header.key"
  #[`${header.key}-header`]="{ column }"
>
  Slot of "{{ column }}"
</template>

This would be so helpful... this is my current set up
`

`
I would really prefer it if I could indicate a condition for when the row is selected and present the complete form with validation else default to the table data... This is my implementation of utable with form input

An I deal situation for me is something similar to what primevue did here
https://tailwind.primevue.org/datatable/#cell_edit

@Nyantekyi I'll keep this in mind when building the Table component for v3 😊

Duplicate #818.

Reading the issue you commented above, it doesn't seem to be the same topic. Anyway, I hope it's available in #2139.

@caiotarifa It's implicit, all component in Nuxt UI v3 implements generics 😊

authors: Nyantekyi benjamincanac caiotarifa migro1982

repo: nuxt/ui


text:
Bug with encoding

Hello!
Please, fix this bug.
Problem
(eval):fc:1: no such event: 0
Traceback (most recent call last):
  File "/usr/local/bin/thefuck", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/dist-packages/thefuck/main.py", line 77, in main
    fix_command()
  File "/usr/local/lib/python2.7/dist-packages/thefuck/main.py", line 28, in fix_command
    selected_command = select_command(corrected_commands)
  File "/usr/local/lib/python2.7/dist-packages/thefuck/ui.py", line 106, in select_command
    logs.confirm_text(selector.value)
  File "/usr/local/lib/python2.7/dist-packages/thefuck/logs.py", line 61, in confirm_text
    blue=color(colorama.Fore.BLUE)))
UnicodeEncodeError: 'ascii' codec can't encode characters in position 928-934: ordinal not in range(128)

Soft
The Fuck 3.1 using Python 2.7.10
zsh 5.1.1 (x86_64-ubuntu-linux-gnu)
Distrubive
Distributor ID: Ubuntu
Description:    Ubuntu 15.10
Release:        15.10
Codename:       wily
How to reproduce
Don't know. This problem was on clean OS (just installed os and tools and after that this error shows)
Output with THEFUCK_DEBUG=TRUE
(eval):fc:1: no such event: 0
DEBUG: Run with settings: {'debug': True,
 'env': {'GIT_TRACE': '1', 'LANG': 'C', 'LC_ALL': 'C'},
 'exclude_rules': [],
 'no_colors': False,
 'priority': {},
 'require_confirmation': True,
 'rules': [<object object at 0x7f0fe8ade0d0>],
 'user_dir': PosixPath('/home/user/.thefuck'),
 'wait_command': 3}

And after that I can't enter any command (shell prompt doesn't show)
Anything else
This problem shows only when I open new terminal window, but not when working in shell

Can you post your .zshrc?

@nvbn here is it:
# General config
export LANG=en_US.UTF-8
export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:$PATH"
ZSH_THEME="pygmalion"
export EDITOR='vim'
export ZSH=$HOME/.zsh
#export THEFUCK_DEBUG=true
###Disable AutoUpdate prompt
DISABLE_UPDATE_PROMPT=true
###Plugins
plugins=(copydir, copyfile, cp, git, git-prompt, git-extras, git-remote-branch, gitfast, github, gitignore, history, history-substring-search, sudo, zsh-syntax-highlighting, colored-man, colorize, extract, screen, vi-mode, mercurial, composer)

# Hotkeys
###vi style
	bindkey -v
###emacs style
#bindkey -e

# Aliases
###Console tools
	alias ls='ls --color=auto'
	alias grep='grep --colour=auto'

# Autocomplete
	autoload -U compinit promptinit
	compinit
	promptinit
###Just promt dir path to cd
	setopt autocd
###Show autocomplete menu
	zstyle ':completion:*' menu select=long-list select=0
	zstyle ':completion:*:default' list-colors ${(s.:.)LS_COLORS}
###Correct input
	setopt CORRECT_ALL

# History
###History file
	export HISTFILE=~/.zsh_history
###Max commands saved in session
	export HISTSIZE=1000
	export SAVEHIST=$HISTSIZE
###Enable commands history
	setopt APPEND_HISTORY
###Remove duplicates, emty strings, etc.
	setopt HIST_IGNORE_ALL_DUPS
	setopt HIST_IGNORE_SPACE
	setopt HIST_REDUCE_BLANKS

# Help
	autoload -U run-help
	autoload run-help-git
	autoload run-help-svn
	autoload run-help-svk
	alias help=run-help

# Functions
### Create archive
	pk () {
		if [ $1 ] ; then
			case $1 in
				tbz)       tar cjvf $2.tar.bz2 $2      ;;
		tgz)       tar czvf $2.tar.gz  $2       ;;
		tar)      tar cpvf $2.tar  $2       ;;
		bz2)    bzip $2 ;;
		gz)        gzip -c -9 -n $2 > $2.gz ;;
		zip)       zip -r $2.zip $2   ;;
		7z)        7z a $2.7z $2    ;;
		*)         echo "'$1' cannot be packed via pk()" ;;
		esac
		else
			echo "'$1' is not a valid file"
				fi
	}

# Source Oh My Zsh
	source $ZSH/oh-my-zsh.sh
eval TF_ALIAS=fuck alias fuck='eval $(thefuck $(fc -ln -1 | tail -n 1)); fc -R'
eval alias fuck='TF_ALIAS=fuck eval $(thefuck $(fc -ln -1))'

Try to replace:
eval TF_ALIAS=fuck alias fuck='eval $(thefuck $(fc -ln -1 | tail -n 1)); fc -R'
eval alias fuck='TF_ALIAS=fuck eval $(thefuck $(fc -ln -1))'

with:
eval "$(thefuck --alias)"

Thank you! This variant works!
pS: Please, update docs for zsh, because I got bugged variant from your wiki

Same error, tried cd sr (the correct dir name is src) and then fuck:
 oskar@Oskars-iMac  ~  cd sr
cd: no such file or directory: sr
 ✘ oskar@Oskars-iMac  ~  fuck
DEBUG: Run with settings: {'debug': True,
 'env': {'GIT_TRACE': '1', 'LANG': 'C', 'LC_ALL': 'C'},
 'exclude_rules': [],
 'no_colors': False,
 'priority': {},
 'require_confirmation': True,
 'rules': [<object object at 0x105026160>],
 'user_dir': PosixPath('/Users/oskar/.config/thefuck'),
 'wait_command': 3}
DEBUG: Received stdout:
DEBUG: Received stderr: /bin/sh: line 0: cd: sr: No such file or directory

DEBUG: Call: cd sr; with env: {'LESS': '-R', 'VERSIONER_PYTHON_PREFER_32_BIT': 'no', 'LC_CTYPE': '', 'LOGNAME': 'oskar', 'USER': 'oskar', 'PATH': '/usr/local/bin:/Users/oskar/bin:/usr/bin:/bin:/usr/sbin:/sbin', 'HOME': '/Users/oskar', 'ZSH': '/Users/oskar/.oh-my-zsh', 'TERM_PROGRAM': 'iTerm.app', 'LANG': 'C', 'THEFUCK_DEBUG': 'TRUE', 'TERM': 'xterm-256color', 'Apple_PubSub_Socket_Render': '/private/tmp/com.apple.launchd.tJ83YfY5Lr/Render', 'COLORFGBG': '12;8', 'VERSIONER_PYTHON_VERSION': '2.7', 'SHLVL': '0', 'SECURITYSESSIONID': '186a8', 'XPC_FLAGS': '0x0', 'ITERM_SESSION_ID': 'w0t1p0', '_': '/usr/local/bin/thefuck', 'SSH_AUTH_SOCK': '/private/tmp/com.apple.launchd.GmOUBAfWd3/Listeners', 'PYTHONPATH': '/usr/local/Cellar/thefuck/3.2/libexec/lib/python2.7/site-packages:/usr/local/Cellar/thefuck/3.2/libexec/vendor/lib/python2.7/site-packages', 'XPC_SERVICE_NAME': '0', 'SHELL': '/bin/zsh', 'ITERM_PROFILE': 'Default', 'LC_ALL': 'C', 'TMPDIR': '/var/folders/xb/lz_hwys161b_pg3_hyckstpw0000gn/T/', 'LSCOLORS': 'Gxfxcxdxbxegedabagacad', 'GIT_TRACE': '1', '__CF_USER_TEXT_ENCODING': '0x1F5:0x0:0x0', 'PWD': '/Users/oskar', 'PAGER': 'less'}; took: 0:00:00.002986
DEBUG: Importing rule: apt_get; took: 0:00:00.000181
DEBUG: Importing rule: apt_get_search; took: 0:00:00.000289
DEBUG: Importing rule: brew_install; took: 0:00:00.000323
DEBUG: Importing rule: brew_unknown_command; took: 0:00:00.000106
DEBUG: Importing rule: brew_upgrade; took: 0:00:00.000038
DEBUG: Importing rule: cargo; took: 0:00:00.000035
DEBUG: Importing rule: cargo_no_command; took: 0:00:00.000189
DEBUG: Importing rule: cd_correction; took: 0:00:00.000786
DEBUG: Importing rule: cd_mkdir; took: 0:00:00.000273
DEBUG: Importing rule: cd_parent; took: 0:00:00.000040
DEBUG: Importing rule: composer_not_command; took: 0:00:00.000203
DEBUG: Importing rule: cp_omitting_directory; took: 0:00:00.000287
DEBUG: Importing rule: cpp11; took: 0:00:00.000183
DEBUG: Importing rule: dirty_untar; took: 0:00:00.001115
DEBUG: Importing rule: dirty_unzip; took: 0:00:00.000204
DEBUG: Importing rule: django_south_ghost; took: 0:00:00.000051
DEBUG: Importing rule: django_south_merge; took: 0:00:00.000050
DEBUG: Importing rule: docker_not_command; took: 0:00:00.000310
DEBUG: Importing rule: dry; took: 0:00:00.000051
DEBUG: Importing rule: fix_alt_space; took: 0:00:00.000193
DEBUG: Importing rule: fix_file; took: 0:00:00.001827
DEBUG: Importing rule: git_add; took: 0:00:00.000343
DEBUG: Importing rule: git_branch_delete; took: 0:00:00.000202
DEBUG: Importing rule: git_branch_list; took: 0:00:00.000190
DEBUG: Importing rule: git_checkout; took: 0:00:00.000199
DEBUG: Importing rule: git_diff_staged; took: 0:00:00.000187
DEBUG: Importing rule: git_fix_stash; took: 0:00:00.000268
DEBUG: Importing rule: git_not_command; took: 0:00:00.000211
DEBUG: Importing rule: git_pull; took: 0:00:00.000196
DEBUG: Importing rule: git_pull_clone; took: 0:00:00.000190
DEBUG: Importing rule: git_push; took: 0:00:00.000188
DEBUG: Importing rule: git_push_force; took: 0:00:00.000188
DEBUG: Importing rule: git_push_pull; took: 0:00:00.000187
DEBUG: Importing rule: git_stash; took: 0:00:00.000184
DEBUG: Importing rule: git_two_dashes; took: 0:00:00.000188
DEBUG: Importing rule: go_run; took: 0:00:00.000169
DEBUG: Importing rule: grep_recursive; took: 0:00:00.000176
DEBUG: Importing rule: gulp_not_task; took: 0:00:00.000187
DEBUG: Importing rule: has_exists_script; took: 0:00:00.000178
DEBUG: Importing rule: heroku_not_command; took: 0:00:00.000174
DEBUG: Importing rule: history; took: 0:00:00.000051
DEBUG: Importing rule: java; took: 0:00:00.000153
DEBUG: Importing rule: javac; took: 0:00:00.000151
DEBUG: Importing rule: lein_not_task; took: 0:00:00.000254
DEBUG: Importing rule: ls_lah; took: 0:00:00.000215
DEBUG: Importing rule: man; took: 0:00:00.000145
DEBUG: Importing rule: man_no_space; took: 0:00:00.000033
DEBUG: Importing rule: mercurial; took: 0:00:00.000152
DEBUG: Importing rule: mkdir_p; took: 0:00:00.000153
DEBUG: Importing rule: mvn_no_command; took: 0:00:00.000144
DEBUG: Importing rule: mvn_unknown_lifecycle_phase; took: 0:00:00.000153
DEBUG: Importing rule: no_command; took: 0:00:00.000155
DEBUG: Importing rule: no_such_file; took: 0:00:00.000038
DEBUG: Importing rule: open; took: 0:00:00.000168
DEBUG: Importing rule: pacman; took: 0:00:00.000192
DEBUG: Importing rule: pacman_not_found; took: 0:00:00.000069
DEBUG: Importing rule: pip_unknown_command; took: 0:00:00.000210
DEBUG: Importing rule: python_command; took: 0:00:00.000154
DEBUG: Importing rule: python_execute; took: 0:00:00.000147
DEBUG: Importing rule: quotation_marks; took: 0:00:00.000032
DEBUG: Importing rule: rm_dir; took: 0:00:00.000165
DEBUG: Importing rule: rm_root; took: 0:00:00.000176
DEBUG: Importing rule: sed_unterminated_s; took: 0:00:00.000162
DEBUG: Importing rule: sl_ls; took: 0:00:00.000030
DEBUG: Importing rule: ssh_known_hosts; took: 0:00:00.000160
DEBUG: Importing rule: sudo; took: 0:00:00.000035
DEBUG: Importing rule: switch_lang; took: 0:00:00.000047
DEBUG: Importing rule: systemctl; took: 0:00:00.000260
DEBUG: Importing rule: test.py; took: 0:00:00.000030
DEBUG: Importing rule: tmux; took: 0:00:00.000153
DEBUG: Importing rule: touch; took: 0:00:00.000229
DEBUG: Importing rule: tsuru_login; took: 0:00:00.000145
DEBUG: Importing rule: tsuru_not_command; took: 0:00:00.000146
DEBUG: Importing rule: unknown_command; took: 0:00:00.000034
DEBUG: Importing rule: vagrant_up; took: 0:00:00.000156
DEBUG: Importing rule: whois; took: 0:00:00.000196
DEBUG: Trying rule: dry; took: 0:00:00.000068
DEBUG: Trying rule: test.py; took: 0:00:00.000010
DEBUG: Trying rule: apt_get_search; took: 0:00:00.000315
DEBUG: Trying rule: brew_install; took: 0:00:00.000012
DEBUG: Trying rule: brew_unknown_command; took: 0:00:00.000008
DEBUG: Trying rule: brew_upgrade; took: 0:00:00.000007
DEBUG: Trying rule: cargo; took: 0:00:00.000007
DEBUG: Trying rule: cargo_no_command; took: 0:00:00.000092
DEBUG: Trying rule: cd_correction; took: 0:00:00.000094
DEBUG: Total took: 0:00:00.025918
Traceback (most recent call last):
  File "/usr/local/Cellar/thefuck/3.2/libexec/bin/thefuck", line 9, in <module>
    load_entry_point('thefuck==3.2', 'console_scripts', 'thefuck')()
  File "/usr/local/Cellar/thefuck/3.2/libexec/lib/python2.7/site-packages/thefuck/main.py", line 77, in main
    fix_command()
  File "/usr/local/Cellar/thefuck/3.2/libexec/lib/python2.7/site-packages/thefuck/main.py", line 28, in fix_command
    selected_command = select_command(corrected_commands)
  File "/usr/local/Cellar/thefuck/3.2/libexec/lib/python2.7/site-packages/thefuck/ui.py", line 106, in select_command
    logs.confirm_text(selector.value)
  File "/usr/local/Cellar/thefuck/3.2/libexec/lib/python2.7/site-packages/thefuck/logs.py", line 61, in confirm_text
    blue=color(colorama.Fore.BLUE)))
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2191' in position 56: ordinal not in range(128)

Using zsh with eval "$(thefuck --alias)" in my .zshrc.
Installed thefuck with brew: The Fuck 3.2 using Python 2.7.10

Experiencing the same issue all of a sudden. Not exactly sure what changed, other than maybe the brew being updated.
LvH-MBP:~ liroy$ grip
-bash: grip: command not found
LvH-MBP:~ liroy$ fuck
Traceback (most recent call last):
File "/usr/local/bin/thefuck", line 11, in
sys.exit(main())
File "/usr/local/lib/python2.7/site-packages/thefuck/main.py", line 77, in main
fix_command()
File "/usr/local/lib/python2.7/site-packages/thefuck/main.py", line 28, in fix_command
selected_command = select_command(corrected_commands)
File "/usr/local/lib/python2.7/site-packages/thefuck/ui.py", line 106, in select_command
logs.confirm_text(selector.value)
File "/usr/local/lib/python2.7/site-packages/thefuck/logs.py", line 61, in confirm_text
blue=color(colorama.Fore.BLUE)))
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2191' in position 39: ordinal not in range(128)

authors: CoreISP nvbn prewk rakshazi

repo: nvbn/thefuck

license: mit

license_source: bigquery


text:
Fix issues for VisibleBoundsPadding when it's applied on a ScrollViewer

Issue:

https://nventive.visualstudio.com/Umbrella/_workitems/edit/132021
https://nventive.visualstudio.com/Umbrella/_workitems/edit/132032
https://nventive.visualstudio.com/Umbrella/_workitems/edit/132087
PR Type
What kind of change does this PR introduce?

Bugfix

What is the current behavior?

Padding is not set properly if it is applied to a ScrollViewer component (including ListView)
What is the new behavior?
Padding is not set properly
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tested code with current supported SDKs
[x] Docs have been added/updated which fit documentation template. (for bug fixes / features)
[ ] Tests for the changes have been added (for bug fixes / features) (if applicable)
[x] Contains NO breaking changes

These changes don't apply to ScrollViewer, only ListView specifically. They're also not specific to VisibleBoundsPadding, they're relevant whenever Padding is changed or when a top Padding is initially set.
Otherwise looks good. ;)

source: gharchive/pull-request

authors: YGuerin davidjohnoliver

repo: nventive/Uno


text:
🛑 NVIDIA AI Enterprise Hub is down

In 0350027, NVIDIA AI Enterprise Hub (https://nvaie.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NVIDIA AI Enterprise Hub is back up in c8341c6.

repo: nvgsg/lab-upptime


text:
🛑 PufferAI HPC Portal is down

In a3eac38, PufferAI HPC Portal (https://hpc.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PufferAI HPC Portal is back up in 2de836a.


text:
🛑 NVIDIA AI Enterprise Hub is down

In 409c21f, NVIDIA AI Enterprise Hub (https://nvaie.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NVIDIA AI Enterprise Hub is back up in be911f0.


text:
🛑 Kubeflow ML Platform is down

In 930cf16, Kubeflow ML Platform (https://kubeflow.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kubeflow ML Platform is back up in 04a680a.


text:
Issue #204-Fixed

Majority of new installs throwing this error
ERROR
No specs found for module custom.plugins
SITUATION
Normal usage of nvim
ORIGIN
Line : 187 throws error guarantied, as there is no custom.plugins plugins plugin, it's just syntax ref for future purposes.
FIX
1.Just commented the line that's causing error
2.Mentioned it is a syntax, to add plugins in future, as it was intended.

Hi! Thanks for your contribution!
As per README.md you must actually install the entirety of the kickstart.nvim files into your config in order for things to work.
Just copying in init.lua isn't supported with the current distribution.
Closing. Please feel free to re-open if you disagree.


text:
Add additional symbol kinds for current_function

Resolves #48.
This is a larger list of symbol kinds than the original issue, but I think it's justified. These kinds all tend to be top-level, which means you wouldn't lose other information by including these.

Is it possible to use default require('vim.lsp.protocol').CompletionItemKind? It is not very convenient to set this setting twice.

@Shatur95 Won't that cause issues if users customize CompletionItemKind (e.g. via https://github.com/onsails/lspkind-nvim)?
Also, right now, this is nothing extra to configure. Are you referring to customizing how the current symbol is displayed, or filtering the set of symbol kinds to display?

@Shatur95 Won't that cause issues if users customize CompletionItemKind (e.g. via https://github.com/onsails/lspkind-nvim)?

No, this plugins just sets CompletionItemKind in an ordinary way, so should work ^)

Also, right now, this is nothing extra to configure. Are you referring to customizing how the current symbol is displayed, or filtering the set of symbol kinds to display?

I was referring to the display settings. I need to set CompletionItemKind and kind_labels separately. But, probably, this is okay, because by default, CompletionItemKind contains just text without icons.

Ah - I think this is actually a different issue, that of unifying kind_labels and CompletionItemKind. I would definitely be OK with using CompletionItemKind as a default for kind_labels, but I think that should happen in a separate PR - this PR is just about expanding the set of kinds which may be displayed, not changing how they're displayed.

(+1 to using CompletionItemKind as a default - I think kind_labels should still be configurable, because you might want different labels on your statusline vs for completion items - but I agree that this is completely orthogonal to this PR.)

I think this is good to go. Thanks, @nihilistkitten!

authors: Shatur95 nihilistkitten wbthomason


text:
Bug: Trying to display file icon and path=1 or path=2 but lua throwing error.

Self Checks

[x] I'm using the latest lualine.
[x] I didn't find the issue in exsisting issues or prs.

How to reproduce the problem

I am using almost default config and not complicated configuration as below;
-- lualine config
require'lualine'.setup {
      options = {
        icons_enabled = true,
        theme = 'everforest',
        component_separators = { left = '', right = ''},
        section_separators = { left = '', right = ''},
        disabled_filetypes = {},
        always_divide_middle = true,
      },
      sections = {
        lualine_a = {'mode'},
        lualine_b = {'branch', 'diff',
                      {'diagnostics', sources={'nvim_lsp', 'coc'}}},
        lualine_c = {
                        'filename',
                        file_status = true,  -- displays file status (readonly status, modified status)
                        path = 1,            -- 0 = just filename, 1 = relative path, 2 = absolute path
                        shorting_target = 40 -- Shortens path to leave 40 space in the window
                           -- for other components. Terrible name any suggestions?
                      },
        lualine_x = {'filetype'},
        lualine_y = {},
        lualine_z = {'location'}
      },
      inactive_sections = {
        lualine_a = {},
        lualine_b = {},
        lualine_c = {'filename'},
        lualine_x = {'location'},
        lualine_y = {'progress'},
        lualine_z = {}
      },
      tabline = {},
      extensions = {}
    }

Expected behaviour
I expect a relative path and the icon next to this path
Actual behaviour
Getting;
E5108: Error executing lua ...toload/plugged/lualine.nvim/lua/lualine/utils/loader.lua:134: attempt to index local 'component' (a number value)
error.
Minimal config to reproduce the issue

Config
<!--
  =================
  ### IMPORTENT ###
  =================
<p>You need to provide a way to reproduce the issue without influence
of other plugins.
Issues without proper format and a proper way to
reproduce might be ignored.
This script can help you with that.
https://github.com/nvim-lualine/lualine.nvim/blob/master/scripts/nvim_isolated_conf.sh
Create an isolated config directory with:
`nvim_isolated_conf.sh -c DirectoryName`

Then modify the DirectoryName/.config/nvim/init.vim
so you can reproduce the issue .
You can load the config to see if the issue is occuring with
`nvim_isolated_conf.sh -l DirectoryName`

Paste the DirectoryName/.config/init.vim without comments below
-->

Aditional information
Thanks.

It's suppose to be
lualine_c = {
                        {'filename',
                        file_status = true,  -- displays file status (readonly status, modified status)
                        path = 1,            -- 0 = just filename, 1 = relative path, 2 = absolute path
                        shorting_target = 40 -- Shortens path to leave 40 space in the window
                           -- for other components. Terrible name any suggestions?
                      }},

notice the extra {} for options.

Thanks that did the trick.

authors: MustafaErgul shadmansaleh


text:
Question: is it expected that inner function objects include braces?

(Thanks for the plugin: it is a snap to set up and easy to work with so far.)
I was surprised to see that by default, an inner function object in, for example, Go and Javascript includes the braces. I'm guessing that this is expected behavior and probably a result of how treesitter itself works. But I wanted to confirm that before going further.
I ask because my most common use for inner function objects is that I want to change, delete, or yank all the code in the function body, but in those cases I don't normally want to include the braces. So, I'll need to consider whether it's possible to tweak treesitter's results.

They shouldn't include braces. Depending on the grammar this could be easy to fix or not... For js and go, looks like it require for us to support the */+ operators.
(function_declaration
  body: (statement_block . "{" (_)* @function.inner . "}")) @function.outer

Could also be fixed by the grammar to not include braces inside the block node.

Looks like we have the same problem with C :/

I don't think that linewise makes sense for ap, since functions can be expressions in many languages, like in the following snippet of javascript:
var x = function() {
  console.log("Hello, world")
}

I do agree that af (and other as) should include whitespace, however.

It is a short-coming that we can only select nodes at the moment. We wanted to trim the braces using a regex directive and use that solution also for language injection. Language injection now uses a hack #offset to trim characters. Would be great when someone could contribute a proper solution!

@dominikh

I don't think that linewise makes sense for ap, since functions can be expressions in many languages

I'm not sure that I'm following, could you please elaborate? Also, did you mean to write ap, or should it be if?

@Melkster
I meant to write af, not ap. And my point was that if af acted linewise, then doing something like daf inside the function in
var x = function() {
  console.log("Hello, world")
}

would delete more than just the function.

Perhaps there should be an additional command for a linewise "around function" text-object, for instance Af, kinda like how targets.vim allows an upper-case "around" to do things like A(, A{, which includes any trailing whitespace.
I personally think that it would be a super useful feature to be able to move around functions using a single text-object which gets the whitespace right immediately, just like one can do with paragraphs and ap.

[M]y point was that if af acted linewise, then doing something like daf inside the function in
var x = function() {
console.log("Hello, world")
}

would delete more than just the function.

@dominikh At first thought, I think that daf should delete more than the function there. If someone wanted only to rewrite the content of the anonymous function, they would use cif, right?
That said, I suppose that you're leaving room for cases where people want to replace the entire anonymous function and assign x to a named function or some other value?
For whatever it's worth, I'm back to using the object mappings in vim-go (which rely on fatih's motion), and vaf selects from sayHelloWorld to the closing } in the Go code below. I think I understand what you want, but this result basically matches my expectations. (There are issues there too though: if the cursor is on sayHelloWorld, vim-go does not see that line as the beginning of a function. vaf selects the entire function that sayHelloWorld is in. Similarly, if you use var sayHelloWorld = func… at package level, vaf with the cursor on var or sayHelloWorld is a no-op. Whether at package level or within a function, selection of anonymous functions assigned to variables only works once the cursor is at func on the first line or later.)
	sayHelloWorld := func(userName string) {
		fmt.Println("Hello", userName)
	}

daf should really only delete the actual function. To delete line-wise you can use dVaf. Maybe one could have an option for users to make certain mappings automaticly line-wise.

I'm trying to exclude the braces for go based on the above suggestion, the it didn't match the inner function (or block of code actually). I've tried these variations:
(function_declaration
  body: (block . "{" (_)* @function.inner . "}")) @function.outer

And
(func_literal
  body: (block . "{" (_)* @function.inner . "}")) @function.outer

I have the latest Neovim and all related plugins in my setup.
Thank you.

@arsham I haven't found a solution yet with this repository, but you may find nvim-treesitter-textsubjects helpful. (It only works for a handful of languages so far, but it's inner object works well with go.)

@stsewd @theHamsta until * and + are supported for captures, would you consider a patch that uses the pattern from nvim-treesitter-textsubjects for inner functions? It definitely seems like the consensus that an inner function text object should not include the braces. The following work well for go, for example. (I think I should be able to write this as one query using alteration, but I can't get it right.)
(function_declaration
  (block . "{" . (_) @_start @_end (_)? @_end . "}"
         (#make-range! "myfunction.inner" @_start @_end)))

(method_declaration
  (block . "{" . (_) @_start @_end (_)? @_end . "}"
         (#make-range! "myfunction.inner" @_start @_end)))

(func_literal
  (block . "{" . (_) @_start @_end (_)? @_end . "}"
         (#make-range! "myfunction.inner" @_start @_end)))

Would be ok. If possible all "{" should be patched

If possible all "{" should be patched

Yup, understood. I'm not sure how many of those languages I would immediately recognize as such, but I can do several, start a PR, and then get feedback about others to fill in. I'm happy to do that if it works for people.

This is still broken/wrong for @function.inner in Rust, and @block.inner. Both include the curly braces.

This is still broken/wrong for @function.inner in Rust, and @block.inner. Both include the curly braces.

Yup. Unfortunately as I mentioned soon after, I didn't think to include Rust. I don't use the language, and I didn't realize that it was affected when I first made the pull request.
There are other ways in which my initial pull request probably needs to be expanded. I meant to do that myself, but I frankly forgot.
I definitely won't get to this quickly (I'm a teacher, and it's recommendation-writing season), but by looking at the changes I made to other languages, someone else could probably fix Rust pretty quickly. (You can also test it locally on your machine if you follow the instructions to override predefined textobjects.)

Ah, I see, I missed your comment!
Thanks for the pointers, I'll give it a try myself (if/when I've got the time 😅).

This PR #314 should solve this issue

I have the same issue with c#

I have the same issue with c#

I don't use C#, please verify this work for you #318

I do not know if it's related but in c/cpp @block.inner includes braces #589

authors: Goxore Melkster arsham dominikh icyd ilan-schemoul jjant stsewd telemachus theHamsta


text:
Replacing application source code files for delta updates

I am trying to figure out implementing auto updates for nw.js application and at the moment i am on linux/ubuntu. I am building my app named 'nw-autoupdater-demo' using sdk flavor of nw.js binary and it creates a folder with all the files inside it which looks something like this

I am using nw-autoupdater to roll out my updates and i do not wish to send nw.js binary everytime user needs to update to a newer version because the changes are related to just my js/html/css source code only. So i figured out if there's a specific file that contains my application code which i can replace with a newer version and keep the rest of nw.js binaries intact then that would solve my issue.
But from the above figure i cannot figure out which file contains my application code. I tried replacing the main executable file nw-autoupdater-demo with a changed version of my code in a older build created using nw-builder and it works !
Is this the correct approach to make changes to the app and issue updates ?
Is the main executable file the only file i need to replace to update my application source and it would just work ?

@adam-lynch can you shed some light on my query ?

This stuff is really interesting but I'm afraid I can't help much. I'm not sure about Linux I'm sorry :/, I'm not sure where your source goes. Even on Windows & Mac this is tricky because it can trigger the OS / anti-virus, especially if your app is signed. Electron does it nicely (only for Mac & Windows). I think people usually go down the route of publishing their app to package managers instead (e.g. using AppImage or something) rather than having an auto-updater with delta updates. Maybe you could build two simple apps and compare the output to see which files depend on your source?

Quite an old issue this but when I have been messing around with builds on Linux I tend to use the unzipped option in NWB and this creates a package.nw folder alongside all the files in the snapshot above and it is this folder that holds all the app files. I would have thought that if I used the auto-updater to update the app alone then all I would need to do is replace the package.nw folder.
A separate package.nw folder will of course increase the size of the overall distro build.
Cheers,
Blane

authors: Blatman adam-lynch vinaynb

repo: nwjs-community/nw-builder


text:
Add - new snippet: Reusing existing custom pipes

Here is a new snippet. Hope you like it :)

Closes #86


text:
[Agenda] Metadata as list in event description

Adds Event Metadata to descriptions in agenda events
License
I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@heathergh thanks for your review; tests added

Absolutely can't believe I didn't make a "PR not found" joke for this one.

repo: nylas/components


text:
Replace Google Maps iframe with Google Static Map image(s)

This PR fixes #36 and adds a dynamically generated Google Static Map from a new data file: venue.yml
Note: A Google Maps API key is required to unlock 25,000 free requests a day.
Before:

After:

Hey @mermop
I've set up the map partial to only use the Google Maps Key in production mode / build mode - that way you can develop with a map intact.
Spelling errors corrected.
Thanks!

Looks good - merging now - thanks @ndorfin 👍

Hmm, actually -

It's too zoomed in in production - should have checked it in build first, my bad

authors: mermop ndorfin

repo: nzruby/conf


text:
Migrate (Cambridge) users from Google auth to Shibboleth

The Cambridge tenancy is set up with Google auth, and we would like to migrate it to Shibboleth
If we change the authentication method then we need a way to link newly created accounts (using Shib) to the one's belonging to the same users (using GA) so they still have all he same content and access.
We have established that we should be able to link the accounts using EPPN. A node.js script needs to be written to copy user emails for Cambridge from the user profile to a shibboleth login id entry associated to the user.

AKA: Salla's found out about underscore. The script seems to work, but I think some accounts that are not being migrated aren't being recorded in the CSV at the moment, not sure why. Also not sure about whether the structure's right so comments on how to improve very much appreciated.

So, if I understand correctly, we don't currently have a population of cambridge shibboleth accounts in our database. We're preparing to enable cambridge shibboleth in such a way that we won't have a bunch of duplicate accounts created.
If that's correct, the portions of this PR where we are trying to delete a cambridge shibboleth user isn't really necessary.
I think all we need to do is make the new AuthenticationLoginId and AuthenticationUserLoginId entries that allow a user who logs in from shibboleth to be logged in as their existing account based on the gmail authentication.
To do that, we are making the validated assumption that the eppn of users coming in from cambridge shibboleth is identical to the login id that is provided by gmail (i.e., their email address). Therefore, for each user we can look up their gmail address entry in AuthenticationUserLoginId, then add an equivalent cam:shibboleth:mrvisser@cam.ac.uk entry, then add the appropriate reverse mapping in AuthenticationLoginId by associating cam:shibboleth:mrvisser@cam.ac.uk with their user id.
I don't think it's even necessary to delete the existing google login id, as if anything goes wrong, it allows us to re-enable google and the google login ids are still working as they were before.

I've added a commit with just structural changes trying to fix the broken pattern identified by @mrvisser above. I'll have a look at changing the logic to handle the case where no Shibboleth accounts have yet been created next. However, @mrvisser, could you have a look and let me know if I'm on the right track?

_So, if I understand correctly, we don't currently have a population of cambridge shibboleth accounts in our database. We're preparing to enable cambridge shibboleth in such a way that we won't have a bunch of duplicate accounts created.
If that's correct, the portions of this PR where we are trying to delete a cambridge shibboleth user isn't really necessary._
This is correct.
_I think all we need to do is make the new AuthenticationLoginId and AuthenticationUserLoginId entries that allow a user who logs in from shibboleth to be logged in as their existing account based on the gmail authentication.
To do that, we are making the validated assumption that the eppn of users coming in from cambridge shibboleth is identical to the login id that is provided by gmail (i.e., their email address). Therefore, for each user we can look up their gmail address entry in AuthenticationUserLoginId, then add an equivalent cam:shibboleth:mrvisser@cam.ac.uk entry, then add the appropriate reverse mapping inAuthenticationLoginId by associating cam:shibboleth:mrvisser@cam.ac.uk with their user id._
As per the reference to the email thread above we have established as far as possible that this is the case. We should be using eppn as the identification parameter
I don't think it's even necessary to delete the existing google login id, as if anything goes wrong, it allows us to re-enable google and the google login ids are still working as they were before.
Sounds sensible.

Script now creates EPPN-based loginId records for all users with non-duplicated emails.

I've added some feedback, looking good! Assigning back to @sallakarppinen

Changed to take email value from Google loginId plus fixes based on comments.

I've finished a round of review. Now that we have the coding patterns down path here, it would be good to see some unit tests for the migration. A sample of other migration unit tests can be found in test-migration.js. Something along the lines of generating 2 tenants with a good amount of users in it (say, 500 each), then running the migration on one of the tenants and ensuring that the new tenant ids are migrated and the old tenant still has their login id information intact.

@mrvisser: I can't seem to find that test file, can you point me to it please?

@sallakarppinen https://github.com/oaeproject/Hilary/blob/master/node_modules/oae-principals/tests/test-migrations.js

In preparation for the tests, I've split the script into two files (one to run the script and interact with the filesystem, other to actually do the migration). @mrvisser, could you have a quick look and comment when you have a minute?

authors: mrvisser sallakarppinen yojimbo23

repo: oaeproject/Hilary