Sage 8 & Sage 9

sage
1

HI,

Why are we have Sage 8 and Sage 9? Which one should I use it for my new development?

Also When I run watch on Sage 9, it seems does not have Bootstrap Framework anymore?

And it gave me some errors:

                 Asset    Size  Chunks       Chunk Names
      scripts/main.js  493 kB       0       main
scripts/customizer.js  105 kB       1       customizer
  scripts/main.js.map  519 kB       0       main

scripts/customizer.js.map 112 kB 1 customizer
chunk {0} scripts/main.js, scripts/main.js.map (main) 464 kB [rendered]
[0] multi main 52 bytes {0} [built] [1 error]
[1] ./~/html-entities/lib/html5-entities.js 49 kB {0} {1} [built]
[2] ./~/ansi-html/index.js 4.02 kB {0} {1} [built]
[3] ./~/ansi-regex/index.js 135 bytes {0} {1} [built]
[4] ./~/css-loader?+sourceMap!./~/postcss-loader!./~/resolve-url-loader?+sourceMap!./~/sass-loader?+sourceMap!./assets/styles/main.scss 376 kB {0} [built]
[5] ./~/html-entities/index.js 231 bytes {0} {1} [built]
[6] ./~/html-entities/lib/html4-entities.js 6.57 kB {0} {1} [built]
[7] ./~/html-entities/lib/xml-entities.js 2.98 kB {0} {1} [built]
[8] ./~/querystring/decode.js 2.4 kB {0} {1} [built]
[9] ./~/querystring/encode.js 2.09 kB {0} {1} [built]
[10] ./~/querystring/index.js 127 bytes {0} {1} [built]
[11] ./~/strip-ansi/index.js 161 bytes {0} {1} [built]
[12] (webpack)-hot-middleware/client-overlay.js 1.73 kB {0} {1} [built]
[13] (webpack)-hot-middleware/client.js?timeout=20000&reload=true 4.49 kB {0} {1} [built]
[14] (webpack)-hot-middleware/process-update.js 3.88 kB {0} {1} [built]
[15] (webpack)/buildin/module.js 251 bytes {0} {1} [built]
[16] ./~/css-loader/lib/css-base.js 1.51 kB {0} [built]
[17] ./assets/styles/main.scss 1.43 kB {0} [built]
[18] ./~/style-loader/addStyles.js 7.15 kB {0} [built]
chunk {1} scripts/customizer.js, scripts/customizer.js.map (customizer) 78.1 kB [rendered]
[0] multi customizer 40 bytes {1} [built] [1 error]
[1] ./~/html-entities/lib/html5-entities.js 49 kB {0} {1} [built]
[2] ./~/ansi-html/index.js 4.02 kB {0} {1} [built]
[3] ./~/ansi-regex/index.js 135 bytes {0} {1} [built]
[5] ./~/html-entities/index.js 231 bytes {0} {1} [built]
[6] ./~/html-entities/lib/html4-entities.js 6.57 kB {0} {1} [built]
[7] ./~/html-entities/lib/xml-entities.js 2.98 kB {0} {1} [built]
[8] ./~/querystring/decode.js 2.4 kB {0} {1} [built]
[9] ./~/querystring/encode.js 2.09 kB {0} {1} [built]
[10] ./~/querystring/index.js 127 bytes {0} {1} [built]
[11] ./~/strip-ansi/index.js 161 bytes {0} {1} [built]
[12] (webpack)-hot-middleware/client-overlay.js 1.73 kB {0} {1} [built]
[13] (webpack)-hot-middleware/client.js?timeout=20000&reload=true 4.49 kB {0} {1} [built]
[14] (webpack)-hot-middleware/process-update.js 3.88 kB {0} {1} [built]
[15] (webpack)/buildin/module.js 251 bytes {0} {1} [built]

ERROR in ./assets/scripts/main.js

/Applications/MAMP/htdocs/setup/wp-content/themes/starter-theme/assets/scripts/main.js
1:1 error Parsing error: The keyword ‘import’ is reserved

:heavy_multiplication_x: 1 problem (1 error, 0 warnings)

ERROR in ./assets/scripts/main.js
Module build failed: Error: Module failed because of a eslint error.

/Applications/MAMP/htdocs/setup/wp-content/themes/starter-theme/assets/scripts/main.js
1:1 error Parsing error: The keyword ‘import’ is reserved

:heavy_multiplication_x: 1 problem (1 error, 0 warnings)

at lint (/Applications/MAMP/htdocs/setup/wp-content/themes/starter-theme/node_modules/eslint-loader/index.js:73:17)
at Object.module.exports (/Applications/MAMP/htdocs/setup/wp-content/themes/starter-theme/node_modules/eslint-loader/index.js:111:3)

@ multi main

ERROR in ./assets/scripts/customizer.js

/Applications/MAMP/htdocs/setup/wp-content/themes/starter-theme/assets/scripts/customizer.js
1:1 error Parsing error: The keyword ‘import’ is reserved

:heavy_multiplication_x: 1 problem (1 error, 0 warnings)

ERROR in ./assets/scripts/customizer.js
Module build failed: Error: Module failed because of a eslint error.

/Applications/MAMP/htdocs/setup/wp-content/themes/starter-theme/assets/scripts/customizer.js
1:1 error Parsing error: The keyword ‘import’ is reserved

:heavy_multiplication_x: 1 problem (1 error, 0 warnings)

at lint (/Applications/MAMP/htdocs/setup/wp-content/themes/starter-theme/node_modules/eslint-loader/index.js:73:17)
at Object.module.exports (/Applications/MAMP/htdocs/setup/wp-content/themes/starter-theme/node_modules/eslint-loader/index.js:111:3)

@ multi customizer
webpack: bundle is now VALID.

Thanks!

2

Well, it takes time to develop each new version of Sage. We keep the most current stable version available while we work on future versions. The current stable version is Sage 8.

Sage 9 is mostly undocumented at this point and it still has a few known issues (as well as pending features) that we would like to resolve before giving it a stable release. We also might implement breaking changes while it’s in development (we’ve already done this a few times).

Most people should still use Sage 8. You should probably use Sage 8. Feel free to tinker with Sage 9 if you want, but we’re not very likely to offer support for it just yet, not while it’s still in development.

2 Likes
3

that is cool. Thanks!

4

Hey @QWp6t ,

I would like to know if Sage 9 will have updated dependencies? Right now both versions 8 and 9 use node 0.12.x and GitHub says both’s devDependencies are out of date. Will there be updated dependencies whenever sage 9 comes with a stable version?And what are pros and cons with the outdated vs up to date ones?

I already got sage 8 running with node 6.x and I’m curious why that is not default since when installing npm dependencies there is a lot of warnings?

5

All of Sage 9’s dependencies are already up to date with the exception of jQuery, which is still on the 1.x branch to keep it consistent with the version of jQuery included with WordPress.

I haven’t tested with all versions of Node, but we’ll most likely require Node 5.x (most recent stable version).