No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Uncaught SyntaxError: Unexpected token export

    Help
    2
    2
    2097
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Samulwong
      Samulwong last edited by

      I init quasar project with CLI below

      quasar init default#webpack1 quasar2nd

      and npm install shows up warning as below:

      npm WARN quasar-framework@0.14.7 requires a peer of quasar-extras@0.x but none is installed. You must install peer dependencies yourself.
      npm WARN karma-sinon-chai@1.3.3 requires a peer of sinon@^2.1.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.

      When I run the quasar dev it compiles without any error or warning.
      But the browser just comes with white blank screen and in Chrome dev tool I found an error as below:

      caught SyntaxError: Unexpected token export
      at Object.<anonymous> (app.js:648)
      at webpack_require (app.js:556)
      at fn (app.js:87)
      at eval (eval at <anonymous> (app.js:672), <anonymous>:7:15)
      at Object.<anonymous> (app.js:672)
      at webpack_require (app.js:556)
      at fn (app.js:87)
      at Object.<anonymous> (app.js:587)
      at webpack_require (app.js:556)
      at app.js:579

      I tried to npm install sinon and quasar-extras but it doesn’t work.

      Would any one can help?

      Btw, when I use default template of quasar, it works well. So I am wondering if I need to further config for integrating quasar with webpack and vue.

      Great thank!

      1 Reply Last reply Reply Quote 0
      • benoitranque
        benoitranque last edited by

        Just a heads up: in my machine I’ve had an issue where not all dependencies are installed on npm install. Try running npm install --only=dev also

        1 Reply Last reply Reply Quote 0
        • First post
          Last post