Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 11 06:42
    sb2nov edited #75
  • Oct 11 00:20
    sb2nov opened #75
  • Sep 04 18:33

    dependabot[bot] on npm_and_yarn

    (compare)

  • Sep 04 18:33
    dependabot[bot] closed #67
  • Sep 04 18:33
    dependabot[bot] commented #67
  • Sep 04 18:33
    dependabot[bot] labeled #74
  • Sep 04 18:33
    dependabot[bot] opened #74
  • Sep 04 18:33

    dependabot[bot] on npm_and_yarn

    Bump handlebars from 4.1.2 to 4… (compare)

  • Jul 20 19:46
    larixer closed #73
  • Jul 20 19:46
    larixer commented #73
  • Jul 20 19:46
    larixer labeled #73
  • Jul 20 14:02
    gromov-io commented #73
  • Jul 20 13:34
    gromov-io opened #73
  • Jul 16 20:49
    dependabot[bot] labeled #72
  • Jul 16 20:49
    dependabot[bot] opened #72
  • Jul 16 20:49

    dependabot[bot] on npm_and_yarn

    Bump lodash from 4.17.14 to 4.1… (compare)

  • Jun 06 19:30
    dependabot[bot] labeled #71
  • Jun 06 19:30
    dependabot[bot] opened #71
  • Jun 06 19:30

    dependabot[bot] on npm_and_yarn

    Bump apollo-server-express from… (compare)

  • Jun 05 11:46
    TeNNoX synchronize #69
Joel Poloney
@joelpoloney
I'm running into an interesting issue where I run "zen build", it errors, but still exits successfully. Causing some issues with my CI tool not detecting build failures. Not sure how to configure this to exit with an error code
Example pastebin: https://pastebin.com/MFnEg34m
I could also put this in the sysgears/zen channel, as well
Joel Poloney
@joelpoloney

I feel I want this webpack option set to true: https://webpack.js.org/configuration/other-options/#bail. But when I add a .zenrc.js file with:

const config = {
  builders: {
    server: {
      webpackConfig: {
        bail: true
      }
    }
  }
}

it doesn't work

Joel Poloney
@joelpoloney
Even adding a "zen" entry to my package.json file doesn't appear to be picking up those changes either...
Joel Poloney
@joelpoloney
Even more interesting... without any zenrc files or config, it fails with code in the web directory but not with code in the server directory
yeah, definitely feels like a bug. I wonder if it's because the server directory is always built before the web directory and it's not following the last exit status code or something
TomPfundt
@TomPfundt
Hi, I'm a student and have just come across the create-apollo-app. For one of my uni projects, I'd like to build it in a docker image and deploy it to an AWS ECS, to run ElasticSearch queries. I have deployed simple front end app nginx images before, but am struggling on writing the Dockerfile to achieve this, as docker is also brand new to me. I was just wondering firstly is it possible to run these both in the same docker image for my application, and secondly if someone could point me in the right direction with the Dockerfile?
Victor Vlasenko
@larixer
Hi @TomPfundt
Though we don’t ship Docker configs with create-apollo-app, we have very similar project to create-apollo-app where we do ship Dockerfile and docker-compose.yml:
Take a look there:
https://github.com/sysgears/apollo-universal-starter-kit/blob/master/docker-compose.prod.yml
https://github.com/sysgears/apollo-universal-starter-kit/blob/master/Dockerfile
I think you should have very similair docker configs
We don’t configure nginx there though, just expose Node app directly
TomPfundt
@TomPfundt
Hi @vlasenko thanks for the information, I will have a look at the stater kit repo!
jbsaeza
@jbsaeza
Hi, I
jbsaeza
@jbsaeza
Hi, I'm a student and I've started a project using your @web configuration. I'm having problems finding the location of the header tag so I can change the title of my app. Help
Victor Vlasenko
@larixer

@jbsaeza Create file src/index.html:

<!DOCTYPE html>
<html>
<head>
    <base href="/">
    <meta charset="utf-8">
    <title><%= htmlWebpackPlugin.options.title %></title>
    <meta name="viewport" content="width=device-width, initial-scale=1">
</head>
<body>
    <div id='root'></div>
</body>
</html>

It will be picked up automatically and you will be able to change the title

Joel Poloney
@joelpoloney
Does anyone know how to attach the VSCode debugger to the node process for the GraphQL code and have source maps read through? When I run my local environment, it puts files in packages/server/build... mainly an index.js and then a index.{hash}.js.map file. I've been struggling to get this in my launch.json file so it has all source maps available
Right now, my launch.json file has a launch type of Attach by Process ID... and then I pick the one that GraphQL is running on. It attaches just fine, but breakpoints aren't working because it can't find the source maps. The error I get is: breakpoint ignored because generated code not found (source map problem?)
Joel Poloney
@joelpoloney
Been trying to follow all the suggestions here: https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_source-maps
Victor Vlasenko
@larixer
Yes, its source map problem
Joel Poloney
@joelpoloney
Do you have any more info?
Victor Vlasenko
@larixer
No, all the info is inside your index.{hash}.js.map and index.js
Joel Poloney
@joelpoloney
I've been playing around with it and have it showing up now but it's finding them, but now getting "Breakpoint set but not yet bound" on all my breakpoints :(
Joel Poloney
@joelpoloney
Aha. There we go
I also needed the --inspect on NodeHmrPlugin
Victor Vlasenko
@larixer
Yep
Joel Poloney
@joelpoloney
Thank you again 🙏
is it ok to leave the --inspect?
Victor Vlasenko
@larixer
yes
absolutely
Joel Poloney
@joelpoloney
ah ok great
I also need to add this to my webpack.config.js in the output map
devtoolModuleFilenameTemplate: 'file://[absolute-resource-path]'
Joel Poloney
@joelpoloney
(you may want to add that info to your Debugging readme)
Victor Vlasenko
@larixer
probably yes, I think in zen I used to have much more sophisticated devtoolModuleFilenameTemplate: for the backend
Joel Poloney
@joelpoloney
Ah... yeah I put this in just the webpack.config.js for the server folder. Works like a charm
Joel Poloney
@joelpoloney
Is there a recommended way of including or accessing static files? I'm trying to use https://github.com/i18next/i18next-xhr-backend for i18n serving and I would typically create a locales folder inside my public folder. But since I don't really have one, I'm not quite sure what's the recommended way of setting this up
I see in the build folder, there's an assets.json file that includes references to static images that I'm importing in my code. Is there a way to hook into that somehow?
Joel Poloney
@joelpoloney
Ah nevermind, it looks like there already is support for this in the webpack.config.js file I have. My locales folder needs to be a sibling of src, not included inside of it
Joel Poloney
@joelpoloney
Actually, it appears they're not actually being bundled in when I run yarn build. Any ideas why not? They're there when I serve locally with Webpack
Victor Vlasenko
@larixer
They are included into js bundle
If you want public folder, you can add CopyWebpackPlugin into webpack.config.js
Joel Poloney
@joelpoloney
Hm.. wondering how I can access them in the js bundle. I'm using the i18next-xhr-backend plugin to pull from a static file, which wasn't working
And hm, I just looked into all the JS files in the bundle... I don't see my strings anywhere 🤔
Victor Vlasenko
@larixer
If you want to access assets in the js bundle, the way to do it in a webpack project is to require them. If you want public folder - the way to do it is to use some webpack plugin, for example CopyWebpackPlugin, I don’t know what is i18next-xhr-backend and how it works
Essentially loads your i18n files automatically from a public folder
Victor Vlasenko
@larixer
Joel Poloney
@joelpoloney
yeah probably for the best. Thanks for the tip!