What I’d really like is to be able to update my “super-minimal-aurelia” repo to include an SSR-variant.
The problem with the skeletons is they have way too much stuff I don’t use or need by default. I’d rather see something that strips out all the unnecessary cruft and just includes the absolute bare necessities to make it build and run successfully as a scaffold I can build on top of.
Maybe we can figure out a way to achieve that? I imagine lots of people would love to have a minimal starting point to work from.
Yeah, still getting the same result with your cavy repo - seems like it must be something to do with ssr-engine?
$ yarn run server
yarn run v0.27.5
warning package.json: "dependencies" has dependency "autoprefixer" with range "^7.1.6" that collides with a dependency in "devDependencies" of the same name with version "^6.3.6"
warning package.json: "dependencies" has dependency "bluebird" with range "^3.4.1" that collides with a dependency in "devDependencies" of the same name with version "^3.5.1"
$ nps webpack.server.ssr.start
nps is executing `webpack.server.ssr.start` : nodemon ./server.js
[nodemon] 1.17.3
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node ./server.js`
Wed, 04 Apr 2018 10:56:00 GMT koa deprecated Support for generators will be removed in v3. See the documentation for examples of how to convert old middleware https://github.com/koajs/koa/blob/master/docs/migration.md at server.js:13:5
Starting server....
Listening at http://localhost:8084/
TypeError: Cannot read property 'reconfigure' of undefined
at start (D:\v2 2017\rquast ssr forks\cavy-website-ssr\node_modules\aurelia-ssr-engine\dist\commonjs\aurelia-ssr-engine.js:53:20)
at Object.render (D:\v2 2017\rquast ssr forks\cavy-website-ssr\node_modules\aurelia-ssr-engine\dist\commonjs\aurelia-ssr-engine.js:25:12)
at D:\v2 2017\rquast ssr forks\cavy-website-ssr\node_modules\aurelia-middleware-koa\dist\commonjs\aurelia-middleware-koa.js:15:37
...
Wow! That’s the first time I’ve seen a project not run at all because of using yarn vs. npm! I did have to add ssr-engine to the dependencies, but I got it building and running now. Thank you.
Thanks for your response. I’m in a bit of a bind and this has become my number 1 priority behind my other 100 priorities. I recently launch iSoPro which in short is a web app for independent software professionals https://isopro.solutions/about. I’ve got to get ssr working with the esnext webpack 1.1.2 skeleton. While this app is generating 0 revenue at this point I’m happy to donate funds if that would help create a nice “how to”. In the mean time I’m going to spend my time trying to get it figure out.
Again I appreciate your response and effort.
–Steve
@sboyd glad SSR works for you. It’s also behind on my priorities at the moment, but I want to see it done because I want to see Aurelia do well. Aurelia is close to perfect for me now with SSR, so I’ll be pushing those fixes once people give me some feedback on if they are okay or not.
@rquast I haven’t gotten it working just yet. I was hoping that there was already some good documentation out there on how to add it to the skeleton I started with, and thanks for the iSoPro support. Feel free to refer any contractors you may know to it. I’m hoping to build a really solid community of independents.
Hi rquast
any news regarding implementation of SSR in aurelia CLI ( it will be assume if so, think it will bring aurelia to easy implementation of SSR to accomodate SEO demands other then Google
(and unfortunately some important crawler engines do not support JS FW driven sites ! )
@rquast Your changes are fantastic. You should add those into a PR if you haven’t already because I think they offer considerable value to the SSR functionality.