Skip to content

2.x to 3.x upgrade error

Solved Technical Support
  • Hi,

    I'm getting the below on a v2.x dev install to v.3

      - 1:9  root stylesheet
        at handleCompileResponse (/home/ubuntu/nodebb/node_modules/sass-embedded/dist/lib/src/compile.js:227:15)
        at compileRequestAsync (/home/ubuntu/nodebb/node_modules/sass-embedded/dist/lib/src/compile.js:115:16)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async Object.buildCSS (/home/ubuntu/nodebb/src/meta/minifier.js:161:21)
        at async executeAction (/home/ubuntu/nodebb/src/meta/minifier.js:139:9)
        at async Minifier.css.bundle (/home/ubuntu/nodebb/src/meta/minifier.js:193:9)
        at async CSS.buildBundle (/home/ubuntu/nodebb/src/meta/css.js:221:23)
        at async client side styles (/home/ubuntu/nodebb/src/meta/build.js:36:3)
        at async step (/home/ubuntu/nodebb/src/meta/build.js:117:3)
        at async buildTargets (/home/ubuntu/nodebb/src/meta/build.js:105:4)
    2023-04-03T11:57:41.204Z [4567/177237] - error: Error: Error: Can't find stylesheet to import.
      ╷
    1 │ @import "bootswatch/dist/readable/variables";
      │         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      ╵
      - 1:9  root stylesheet
        at handleCompileResponse (/home/ubuntu/nodebb/node_modules/sass-embedded/dist/lib/src/compile.js:227:15)
        at compileRequestAsync (/home/ubuntu/nodebb/node_modules/sass-embedded/dist/lib/src/compile.js:115:16)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async Object.buildCSS (/home/ubuntu/nodebb/src/meta/minifier.js:161:21)
        at async executeAction (/home/ubuntu/nodebb/src/meta/minifier.js:139:9)
        at async Minifier.css.bundle (/home/ubuntu/nodebb/src/meta/minifier.js:193:9)
        at async CSS.buildBundle (/home/ubuntu/nodebb/src/meta/css.js:221:23)
        at async client side styles (/home/ubuntu/nodebb/src/meta/build.js:36:3)
        at async step (/home/ubuntu/nodebb/src/meta/build.js:117:3)
        at async buildTargets (/home/ubuntu/nodebb/src/meta/build.js:105:4)
    

    Any ideas ?

    Thanks

  • Does this happen during ./nodebb build or when you try to access the site? Seems like it is trying to build the readable skin from bootswatch. That skin no longer exists in bootswatch 5.x it might have been renamed to something else.

  • I get a different error attempting to switch the default theme to slick

        at async buildTargets (/home/ubuntu/nodebb/src/meta/build.js:105:4) {"date":"Mon Apr 03 2023 12:17:18 GMT+0000 (Coordinated Universal Time)","error":{"sassMessage":"Can't find stylesheet to import.","sassStack":"- 5:9  root stylesheet\n","span":{"context":"@import \"./scss/overrides\";\n","end":{"column":26,"line":4,"offset":126},"start":{"column":8,"line":4,"offset":108},"text":"\"./scss/overrides\""}},"exception":true,"os":{"loadavg":[0.59,0.32,0.22],"uptime":784329.6},"process":{"argv":["/usr/bin/node","/home/ubuntu/nodebb/nodebb","upgrade"],"cwd":"/home/ubuntu/nodebb","execPath":"/usr/bin/node","gid":1000,"memoryUsage":{"arrayBuffers":19436434,"external":21497066,"heapTotal":102318080,"heapUsed":74660488,"rss":171380736},"pid":177834,"uid":1000,"version":"v18.15.0"},"stack":"Error: Error: Can't find stylesheet to import.\n\u001b[34m  ╷\u001b[0m\n\u001b[34m5 │\u001b[0m @import \u001b[31m\"./scss/overrides\"\u001b[0m;\n\u001b[34m  │\u001b[0m \u001b[31m        ^^^^^^^^^^^^^^^^^^\u001b[0m\n\u001b[34m  ╵\u001b[0m\n  - 5:9  root stylesheet\n    at handleCompileResponse (/home/ubuntu/nodebb/node_modules/sass-embedded/dist/lib/src/compile.js:231:15)\n    at compileRequestAsync (/home/ubuntu/nodebb/node_modules/sass-embedded/dist/lib/src/compile.js:118:16)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async Object.buildCSS (/home/ubuntu/nodebb/src/meta/minifier.js:161:21)\n    at async executeAction (/home/ubuntu/nodebb/src/meta/minifier.js:139:9)\n    at async Minifier.css.bundle (/home/ubuntu/nodebb/src/meta/minifier.js:193:9)\n    at async CSS.buildBundle (/home/ubuntu/nodebb/src/meta/css.js:219:23)\n    at async client side styles (/home/ubuntu/nodebb/src/meta/build.js:36:3)\n    at async step (/home/ubuntu/nodebb/src/meta/build.js:117:3)\n    at async buildTargets (/home/ubuntu/nodebb/src/meta/build.js:105:4)","trace":[{"column":15,"file":"/home/ubuntu/nodebb/node_modules/sass-embedded/dist/lib/src/compile.js","function":"handleCompileResponse","line":231,"method":null,"native":false},{"column":16,"file":"/home/ubuntu/nodebb/node_modules/sass-embedded/dist/lib/src/compile.js","function":"compileRequestAsync","line":118,"method":null,"native":false},{"column":5,"file":"node:internal/process/task_queues","function":"process.processTicksAndRejections","line":95,"method":"processTicksAndRejections","native":false},{"column":21,"file":"/home/ubuntu/nodebb/src/meta/minifier.js","function":"async Object.buildCSS","line":161,"method":"buildCSS","native":false},{"column":9,"file":"/home/ubuntu/nodebb/src/meta/minifier.js","function":"async executeAction","line":139,"method":null,"native":false},{"column":9,"file":"/home/ubuntu/nodebb/src/meta/minifier.js","function":"async Minifier.css.bundle","line":193,"method":"bundle","native":false},{"column":23,"file":"/home/ubuntu/nodebb/src/meta/css.js","function":"async CSS.buildBundle","line":219,"method":"buildBundle","native":false},{"column":3,"file":"/home/ubuntu/nodebb/src/meta/build.js","function":"async client side styles","line":36,"method":null,"native":false},{"column":3,"file":"/home/ubuntu/nodebb/src/meta/build.js","function":"async step","line":117,"method":null,"native":false},{"column":4,"file":"/home/ubuntu/nodebb/src/meta/build.js","function":"async buildTargets","line":105,"method":null,"native":false}]}
    
  • Maybe the forum default skin set to readable?

  • @baris I've reset it to default - re-trying build

  • @baris seems to work now - not sure why the reset to default didn't work the first time round, but it does now.

  • phenomlabP phenomlab has marked this topic as solved on
  • I've fixed this with an upgrade script so it doesn't crash the build https://github.com/NodeBB/NodeBB/issues/11511

  • @phenomlab said in 2.x to 3.x upgrade error:

    I've reset it to default

    I have a quite similar error while upgrading:

    
    2023-04-30T12:53:19.067Z [4567/226523] - error: [build]         client side styles  build failed
    2023-04-30T12:53:19.068Z [4567/226523] - error: [build] Encountered error during build step
    Error occurred during upgrade: Error: Error: Can't find stylesheet to import.
      ╷
    5 │ @import "./scss/overrides";
      │         ^^^^^^^^^^^^^^^^^^
      ╵
      - 5:9  root stylesheet
        at handleCompileResponse (/home/nodebb/NodeBB/node_modules/sass-embedded/dist/lib/src/compile.js:231:15)
        at compileRequestAsync (/home/nodebb/NodeBB/node_modules/sass-embedded/dist/lib/src/compile.js:118:16)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at async Object.buildCSS (/home/nodebb/NodeBB/src/meta/minifier.js:161:21)
        at async executeAction (/home/nodebb/NodeBB/src/meta/minifier.js:139:9)
        at async Minifier.css.bundle (/home/nodebb/NodeBB/src/meta/minifier.js:193:9)
        at async CSS.buildBundle (/home/nodebb/NodeBB/src/meta/css.js:219:23)
        at async Object.client side styles (/home/nodebb/NodeBB/src/meta/build.js:36:3)
        at async step (/home/nodebb/NodeBB/src/meta/build.js:117:3)
        at async buildTargets (/home/nodebb/NodeBB/src/meta/build.js:105:4)
    (node:226523) UnhandledPromiseRejectionWarning: Error: Error: Can't find stylesheet to import.
      ╷
    5 │ @import "./scss/overrides";
      │         ^^^^^^^^^^^^^^^^^^
      ╵
      - 5:9  root stylesheet
        at handleCompileResponse (/home/nodebb/NodeBB/node_modules/sass-embedded/dist/lib/src/compile.js:231:15)
        at compileRequestAsync (/home/nodebb/NodeBB/node_modules/sass-embedded/dist/lib/src/compile.js:118:16)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at async Object.buildCSS (/home/nodebb/NodeBB/src/meta/minifier.js:161:21)
        at async executeAction (/home/nodebb/NodeBB/src/meta/minifier.js:139:9)
        at async Minifier.css.bundle (/home/nodebb/NodeBB/src/meta/minifier.js:193:9)
        at async CSS.buildBundle (/home/nodebb/NodeBB/src/meta/css.js:219:23)
        at async Object.client side styles (/home/nodebb/NodeBB/src/meta/build.js:36:3)
        at async step (/home/nodebb/NodeBB/src/meta/build.js:117:3)
        at async buildTargets (/home/nodebb/NodeBB/src/meta/build.js:105:4)
    (Use `node --trace-warnings ...` to show where the warning was created)
    (node:226523) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
    (node:226523) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    
    

    Any ideas? Thanks

  • @dave1904 were you using a skin on v2 besides the default? If so, set it back to the default then try the upgrade again as I know some of them were removed in transition from bootstrap 3 to 5

  • Thanks, it was because of the slick theme i think 🙂

  • @dave1904 yes, I don't use that theme but have read similar stories elsewhere on here.

  • This post is deleted!

Suggested Topics


  • Upgrading 3.1.3

    Unsolved Technical Support
    3
    +0
    1 Votes
    3 Posts
    564 Views
    cagatayC
    i think that it was a problem but from now there is no alert. [image: 1684328624025-ee7b6ba6-1b5b-4daf-956f-8bf031f16036-image.png]
  • Console error after upgrade to 2.1.0

    Unsolved Technical Support
    30
    1 Votes
    30 Posts
    3k Views
    phenomlabP
    @baris Which is exactly what I did ! Very odd, but pleased it's fixed, and hope everyone else can benefit from this. Thanks for all the help.
  • Upgrade error 1.17.1 to 1.18.x

    Solved Technical Support
    10
    0 Votes
    10 Posts
    1k Views
    gotwfG
    @pitaj Maybe put a temp note in the install docs since 16.x went LTS today?
  • Upgraded NodeBB To V1.4.2 Errors

    Technical Support
    3
    0 Votes
    3 Posts
    1k Views
    C
    @pichalite Thank you for the response. That was most peculiar, but I reset the config.json to be how it was and it stopped having this error. Besides I still think it's best to check data.config, before extracting data.config.loggedin anyway.
  • Errors upgrading from 1.1.0 to 1.1.2

    Solved Technical Support
    3
    0 Votes
    3 Posts
    2k Views
    G
    Problems in the permission of the files. chown -R [nodebbUser] [nodebbFolder] solved it

Looks like your connection to NodeBB Community was lost, please wait while we try to reconnect.