Dominic Rubas

Results 27 comments of Dominic Rubas

:+1: You saved me a lot of time debugging my RuntimeException.

Same problem here with El Capitan and Elixir 1.2.4. Fixed it with all the above (mix.deps, fix mac path, setting env) **AND** adding autocomplete_server to the confix.exs as described in...

Sounds great! > Also, did you just test by building a production build and looking at bundle size or is there some tooling you used? I'm using a webpack bundle...

@brianzinn Here you go, https://github.com/rubas/nextjs-with-reactbabylonjs - Transpile needed: https://github.com/rubas/nextjs-with-reactbabylonjs/blob/master/next.config.js#L2 - `yarn build` starts the webpack analyzer: https://github.com/rubas/nextjs-with-reactbabylonjs/blob/master/package.json#L9

Is is the [webpack analyzer](https://www.npmjs.com/package/webpack-bundle-analyzer). You can use it with every webpack project. There is a handy plugin for Gatsby as well: https://github.com/JimmyBeldone/gatsby-plugin-webpack-bundle-analyser-v2

![IMG_3656](https://user-images.githubusercontent.com/1042243/182452793-bcc94a79-10d9-49d5-853d-01e58e7c4359.gif) I'm facing the same issue on two machines. I'm suspecting `manage=off layer=above` rules. -- yabai-v4.0.1

Other maybe related errors we see when we run it over all the twig code. Haven't yet figured out what is triggering those. ``` test/node_modules/prettydiff/js/prettydiff.js:13202 (data.token[a].length + data.token[a + 1].length...

Thanks. Helps but that is what `data-prettydiff-ignore` should have been for ..

Yes, as a beautifier should never change the rendered result. Introducing prettydiff to an existing Twig codebase can result in a change of the rendered output, which is not easy...

That looks neat! As long as it is consistent, I'm very happy.