profile
viewpoint

startedantoinevulcain/Financial-Modeling-Prep-API

started time in 12 days

startedFormidableLabs/prism-react-renderer

started time in 13 days

issue closedgatsbyjs/gatsby

No Schema available in GraphiQL under development, which causes a failed build (?)

I'm just facing an error when building, with a cryptic error of WebpackError: The result of this StaticQuery could not be fetched.

Which is likely linked to the fact that when developing, I have NO SCHEMA AVAILABLE under http://localhost:8000/___graphql explorer

This has been buried onto my sites, and appears now when I've deleted node_modules and run yarn again, so I have no idea what is the cause

Actually it happens to all my sites once I delete node_modules and run yarn again

Any idea what can be causing this?

"gatsby": "2.24.2",
"react": "16.13.1",
...
    "**/@emotion/core": "10.0.28",
    "**/@emotion/styled": "10.0.27",
    "**/@mdx-js/mdx": "1.6.6",
    "**/@mdx-js/react": "1.6.6",
    "theme-ui": "0.3.1"

closed time in 17 days

kuworking

issue commentgatsbyjs/gatsby

No Schema available in GraphiQL under development, which causes a failed build (?)

Upgrading to gatsby 2.24.14 solves the thing

kuworking

comment created time in 17 days

issue commentgatsbyjs/gatsby

No Schema available in GraphiQL under development, which causes a failed build (?)

I've been able to reproduce it with the Gatsby Default Starter just by upgrading dependencies

  "dependencies": {
    "gatsby": "2.24.2",
    "react": "16.13.1",
    "react-dom": "16.13.1",
  },
kuworking

comment created time in 17 days

push eventkuworking/wordpress-theme-kuworking-landing-two

kuworking

commit sha 150447228a67cdd89597f6532002da3569afaaa9

.

view details

kuworking

commit sha 9242e341dc3fdf69677d2a67063252fc1999e4a0

typo

view details

push time in 23 days

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 688c06dcbea10aec0e3efa3f4d41c890216db48c

.

view details

kuworking

commit sha cfe6aa9ee587008c6623deba817275af4cfabb5b

.

view details

push time in 23 days

push eventkuworking/wordpress-theme-kuworking-landing-two

kuworking

commit sha 462adac8e4c5fb9f53064d5b1cf58d1113712f23

v0.0.2

view details

push time in 24 days

push eventkuworking/wordpress-theme-kuworking-landing-two

kuworking

commit sha 207678a64e5129093874e335005ed6af8c5a0687

add change of background color

view details

kuworking

commit sha 381edc6b2c437130ea5f65355308d4d5f9130a02

refactor

view details

kuworking

commit sha 883f586ebf2a8f84a550b57a8b05a99e4d4f692f

v0.0.2

view details

push time in 24 days

push eventkuworking/wordpress-theme-kuworking-landing-two

kuworking

commit sha a6f14b52ffae66fc09783c532b752f78570a1af5

v0.0.1

view details

push time in 24 days

create barnchkuworking/wordpress-theme-kuworking-landing-two

branch : master

created branch time in 24 days

created repositorykuworking/wordpress-theme-kuworking-landing-two

created time in 24 days

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha c68ca9a4aece919de879c672b71652c67b37c082

prettier

view details

push time in 25 days

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha ab4c2606a9e0aff09fc922339a46e88ee8caa7b8

remove log

view details

kuworking

commit sha 3b8fbe8b04263cf2574da30cbfc0dd0916c28d33

refactor

view details

kuworking

commit sha 9aee61437082235be764f0cf569bb6bed08f81b5

updated

view details

kuworking

commit sha 4899bb1a752442714ed2ff87a53c15f28b29e7e7

fix twig function

view details

kuworking

commit sha 31f6494e8d6fd519ad402d5067bc7bf0af82ab9f

add composer Timber installation

view details

kuworking

commit sha cbe38f0640eaa0f7eb3a65ebbe9566fb61bdef88

v0.0.8

view details

kuworking

commit sha 4b57f42e368c32f383e01b75965de545c8124a07

v0.0.8

view details

push time in 25 days

startedniutech/node.php

started time in 25 days

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 27167eea35ee45a0360cb96abbb876ccdcb62f36

.

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 3253c963a2a391cf8c285a9fab664a28ffadda6b

.

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 0852cde79e30dfdf092f6047c8b3b475266c2143

eliminated

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 8861ad593680cacdd3c757e63bc5f3e882b5d7dc

responsive

view details

kuworking

commit sha f2184e92c5d5e9a94bea7c5061a8596e79d48885

v0.0.7

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 127d3c4fec46055844ea22ce377dc09d1fbe23f5

fix dot

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha c6e29e162840ee3a1021c6228ec2c8d048d61a36

v0.0.6

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha f6c889b4518d0f81416880473404f8e5111838f4

updated

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha fc388fbb06ef2044639c4ccd5a336bcf1fb05e54

v0.0.6

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha b7c4923cd6075f9fcd4717894916228cab3a5be8

v0.06

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 166b161f49cf9959ef7cf2cbf8d18127ffd3b623

.

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 91232b7edf2af12046e93f55bc1865649feca554

v0.0.6

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 18b8812eb9770099efa7f90d82faa03c8e7ac0a9

new draft

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha db5856da4829975d6bf3532ba474e7edf496380e

new draft

view details

push time in a month

issue commentWordPress/gutenberg

Dynamic blocks: default values for attributes aren't converted into html comments

A little hacky, but you can just conditionally set the default value:

const Editor = props => {
    const { setAttributes, attributes } = props;
    let { myAttribute } = attributes;
    if (!myAttribute) {
       setAttributes({ myAttribute: "foobar" });
   }
   return <div>{myAttribute}</div>;
}

registerBlockType("my/hack", {
  title: "Hack",
  icon: "list",
  category: "common",
  attributes: {
    myAttribute: {
      type: "string"
    }
  },
  edit: props => <Editor {...props} />,
  save: ({ attributes }) => <MyComponent {...attributes} />
});

Wouldn't this work?

registerBlockType('blah', {
  title: 'blah',
  category: 'blah',
  attributes: {
    att1: { type: 'string', default: '' },
    att2: { type: 'string', default: '' },
    att3: { type: 'string', default: '' },
  },
  edit: ({ attributes, setAttributes, className }) => {
    useEffect(() => {
      const initialAttributes = {
        att1: 'blah 1',
        att2: 'blah 2',
        att3: 'blah 3',
      }
      const defaultAttributes = {}
      for (const a in attributes) defaultAttributes[a] = attributes[a] || initialAttributes[a]
      setAttributes(defaultAttributes)
    }, [])
  //...
})
katerlouis

comment created time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 5ea863c1aea664a2670bbc31fd63c2352d5b86d4

next draft

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha 83dc6942999d98e8bf13ae9b4eef49d52fc83473

draft02

view details

push time in a month

startedbrandonweiss/charge

started time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha ae2fce8f18fdf9c3c49b4eb84d1eddff5dda9eca

.

view details

push time in a month

push eventkuworking/wordpress-theme-kuworking-landing-one

kuworking

commit sha d8d1600ffb8186f43d535add3cfc911aef070a21

draft01

view details

kuworking

commit sha fa33bb038a4dd6dd92d6577bc63bb6554bfb046d

Merge branch 'master' of https://github.com/kuworking/wordpress-theme-kuworking-landing-one

view details

push time in a month

create barnchkuworking/wordpress-theme-kuworking-landing-one

branch : master

created branch time in a month

created repositorykuworking/wordpress-theme-kuworking-landing-one

created time in a month

push eventkuworking/kuworking-theme-affiliate

kuworking

commit sha d34761abe0e5038ecad7cfc6e06072646bd7ec59

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-two

kuworking

commit sha 36a61deba2a2fff961a3fe4396c169d83889e78a

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-one

kuworking

commit sha ec6d6d567bb1a0d2b0ea141eb86aadd8c2ad0c3c

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-methods

kuworking

commit sha d9b6d0ae119897f8943d8fcda1e5bdc255fefe61

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-landing-two

kuworking

commit sha e7f714e128d8096948dfa6c7d241fe3a8cabf5e1

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-landing-one

kuworking

commit sha d010bf54dc8dcb2dc6c9185e245ca6246dd137b1

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-core

kuworking

commit sha 03ba31e576673397d0ac445638f6a3aa6711f42e

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-affiliate

kuworking

commit sha f74223c884cfaceff02a79ec013ad5b4f542269b

.

view details

push time in a month

push eventkuworking/kuworking-theme-two

kuworking

commit sha 73e75f1a761c66e0ba4196410bfbe7b195cfc164

.

view details

push time in a month

push eventkuworking/kuworking-theme-one

kuworking

commit sha ee8d632c86e713f5057350a527de942b98e8df23

.

view details

push time in a month

push eventkuworking/kuworking-theme-landing-two

kuworking

commit sha 846cc582dab7e567fa36ac0cff7a3c34d9c5e010

.

view details

push time in a month

push eventkuworking/kuworking-theme-landing-one

kuworking

commit sha 53e5dfe0e65044eeaf142780526e2babc1f8bd28

.

view details

push time in a month

push eventkuworking/kuworking-theme-affiliate

kuworking

commit sha d34761abe0e5038ecad7cfc6e06072646bd7ec59

.

view details

push time in a month

push eventkuworking/kuworking-theme-affiliate

kuworking

commit sha 525864c7e667c11575143fdc1b47116a31aa5f68

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-two

kuworking

commit sha 7c412f56ad8d529408bf67cde0dc6988b696444d

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-one

kuworking

commit sha e2f4f44e3d4448dfa50b48f9aacc85fc83de9212

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-methods

kuworking

commit sha 5bfb5271babe884f450d57b6ee00046242546190

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-landing-two

kuworking

commit sha ff029663989c1fb6f34086a60d8ff9c0035c8b01

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-landing-one

kuworking

commit sha ff25308ea7ec5c34a597b9f89f1e1f9710687901

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-core

kuworking

commit sha d564cb2b3c59f7b3854cb4dc935b6e9d33a3818c

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-affiliate

kuworking

commit sha ea8be1550fe34c56b0f14be9ea8f240620a38eed

.

view details

push time in a month

push eventkuworking/kuworking-theme-two

kuworking

commit sha 017fcdd8c81b11bbfc4927f48b70b7997be40489

.

view details

push time in a month

push eventkuworking/kuworking-theme-one

kuworking

commit sha 088db498d415f77bc0d5a1b72702b622af5c3e50

.

view details

push time in a month

push eventkuworking/kuworking-theme-landing-two

kuworking

commit sha 980037320fe0d1cd24294825122fb83e3e6f00e3

.

view details

push time in a month

push eventkuworking/kuworking-theme-landing-one

kuworking

commit sha f05707b2af6b6473ed33206a16d60bee1e64f6eb

.

view details

push time in a month

push eventkuworking/kuworking-theme-affiliate

kuworking

commit sha 525864c7e667c11575143fdc1b47116a31aa5f68

.

view details

push time in a month

push eventkuworking/kuworking-theme-affiliate

kuworking

commit sha 20b59664646706548cfa75b2dfc3c6103903bb46

.

view details

kuworking

commit sha aa133646e6cef2b70f8e35812b20c75c37a5d8ce

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-two

kuworking

commit sha ff37a05267e1239f8ea088cdb98fa965392db426

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-one

kuworking

commit sha a651589e501c6066c249ef9c08bd087e42b060cf

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-methods

kuworking

commit sha 4a67d1451d1b6eceba351eaca79ab5fb957c04f6

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-landing-two

kuworking

commit sha 4aa945541211bb987cf28894a098ddb2744eb080

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-landing-one

kuworking

commit sha 3961e04b93fa7170da1c4bb73b49b9c6c3228807

.

view details

push time in a month

push eventkuworking/kuworking-theme-one

kuworking

commit sha c442243bf60043f1b8bf885e2bcfcdbed7f65617

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-core

kuworking

commit sha ab0a700f5c9559680e7e294a193c70464422e0b4

.

view details

push time in a month

push eventkuworking/gatsby-theme-kuworking-affiliate

kuworking

commit sha 10aec68c30ead3af77bb1c89252fdd4d3e8fa6e0

.

view details

push time in a month

push eventkuworking/kuworking-theme-two

kuworking

commit sha 13244d0f580b01ad8effbb2a00f51cf9f021056f

.

view details

push time in a month

push eventkuworking/kuworking-theme-landing-two

kuworking

commit sha 6c03ef837f6e662c9ceb4e7f47fe3417c7f24fa2

.

view details

push time in a month

push eventkuworking/kuworking-theme-landing-one

kuworking

commit sha dd360eb41b8910e5725c60b7fe02a1bc92e49f66

.

view details

push time in a month

push eventkuworking/kuworking-theme-affiliate

kuworking

commit sha aa133646e6cef2b70f8e35812b20c75c37a5d8ce

.

view details

push time in a month

issue commentreact-spring/react-spring

Animation is smooth on desktop but slow on Chrome Android

In my case, I see it with useTransition to apply a masonry effect, in an example very similar to the one in the docs

Chrome in desktop fabulous Chrome in Android (Huawei p20 pro) is slow when moving all elements (which are only 10) Chrome in iOS (iPhone 7, much lower resolution) is also slow but experience is way better

To me this is a no-go since I need the experience in mobile as well, and while it is functional, the first impression is too bad

Daniel15

comment created time in a month

startedRareloop/lumberjack

started time in 2 months

issue commentgatsbyjs/gatsby

Worse performance results with Lighthouse v6 (?)

@DannyHinshaw I received this explanation from lighthouse "What I think is going on is that LCP does care about images being fully loaded and the time that's reported is when the image is completely loaded and not when it is first visible. This time can be different due to progressive images and iterative paints."

And then this link, perhaps of help https://web.dev/lcp/#when-is-largest-contentful-paint-reported

kuworking

comment created time in 2 months

issue commentGoogleChromeLabs/squoosh

Is it possible to control a little bit the crop process?

Worst case scenario, you could do it by exporting the cropped image without compressing (I see now that you cannot do it without compressing, but this could be minimal) as many times as you need to crop it before you actually compress it

In my case most of the times I only need a simple adjustment mainly for removing parts of the image, so my 2cents are that a semi-cropping feature to be able to resize while fixing the image origin would be very useful

kuworking

comment created time in 2 months

issue commentGoogleChromeLabs/squoosh

Is it possible to control a little bit the crop process?

With the buttons you could crop from one side, meaning that you could crop several times to achieve the same result as if you had the first option (?)

That being the case, and provided that now there's nothing (forcing users to use another program at least cropping-wise), I'd definitively go for this option 🙌🙌

kuworking

comment created time in 2 months

issue closedAdvancedCustomFields/acf

How to see Gutenberg "blocks" listed in location rules when registered with javascript | and how to get/set those fields from JS (ACF PRO)?

From what I understand, one can

  • Register a Gutenberg block with JavaScript with registerBlockType, where typically one would use a JavaScript-built block to manage everything
  • Register a Gutenberg block with acf_register_block_type to do everything with php

What I would like is to be able to register a block with JavaScript, and then link an ACF to this block in the location section

But there it seems that only those blocks registered with acf_register_block_type are listed

My question is how can I write a block with JS and still use ACF? (maybe obvious, still learning how this works)

-------------edit

I can see the custom fields if I enable them for posts and not for blocks, and set Gutenberg to show custom fields in options

But, what I cannot do is to access and edit these fields from the JS block with getField and the name of the custom field, or providing acf.data.post_id. etc

What am I missing? Or this can only be done with PHP?

closed time in 2 months

kuworking

issue commentAdvancedCustomFields/acf

How to see Gutenberg "blocks" listed in location rules when registered with javascript | and how to get/set those fields from JS (ACF PRO)?

Unneeded

Thanks to https://support.advancedcustomfields.com/forums/topic/how-get-value-by-field-name-in-javascript-api/ in order to access and edit ACF I need the field key, not the name, then I can just build my React block and there use ACF JS API (getField and field.val()) to update the fields

kuworking

comment created time in 2 months

issue openedAdvancedCustomFields/acf

How to see Gutenberg "blocks" listed in location rules when regsitered with javascript (ACF PRO)

From what I understand, one can

  • Register a Gutenberg block with JavaScript with registerBlockType, where typically one would use a JavaScript-built block to manage everything
  • Register a Gutenberg block with acf_register_block_type to do everything with php

What I would like is to be able to register a block with JavaScript, and then link an ACF to this block in the location section

But there it seems that only those blocks registered with acf_register_block_type are listed

My question is how can I write a block with JS and still use ACF? (maybe obvious, still learning how this works)

created time in 2 months

issue commenttimber/timber

post.content function strips inconsistently out iframe if exposed to javascript in $twig->addFunction

Found here https://stackoverflow.com/questions/26750626/how-to-post-post-content-as-html

So I do have to apply the filter

$twig->addFunction(new Timber\Twig_Function('expose_post', function ($post) {
	$content = apply_filters('the_content', $post->post_content);
	return [
		'content' => $content, 
		];
	}));

But I don't understand why do I need to apply the filter here and not if done through twig (through the same method supposedly)

kuworking

comment created time in 2 months

issue openedtimber/timber

post.content function strips inconsistently out iframe if exposed to javascript in $twig->addFunction

Likely it is not a bug, but it could be

The aim: to expose {{ post.content }} to JavaScript

The problem: when done in functions.php, tags as iframe are striped out, where the filter wp_kses_allowed_html doesn't seem to work

What I would expect: that calling the function post.content in php would produce the same result as when called from twig

// this code works, in a page.twig
// the lack of ";" in these 2 lines is necessary
  <script>
    var content = {{post.content|json_encode}}
    var content2 = {{post|json_encode}}
    console.log(content); // iframe is there
    console.log(content2); // iframe is there
  </script>

this code does not work, and cannot find out why

// in page.twig
  <script>
    var content = {{ expose_post(post)|json_encode}}
    console.log(content); // iframe is NOT there
  </script>
// in functions.php
$twig->addFunction(new Timber\Twig_Function('expose_post', function ($post) {
	return [
		'content' => $post->post_content, 
	];
}));

Maybe it is in this filter https://github.com/timber/timber/blob/d160d7a88144969dd196abeb513816a905eea690/lib/Post.php#L1227 but this is happening in both places (?)

My workaround is to expose the content part of the post in twig and not in php, but what is that I am not understanding?

created time in 2 months

issue commentgatsbyjs/gatsby

Worse performance results with Lighthouse v6 (?)

@nandorojo my impression with images is that emulation is done with a really slow connection and there, images do take a long time to be rendered

Since the option of removing images is not always possible, perhaps these 70's scores are the normal ones for this type of pages

And, the option of delaying their loading so that the user can start his interaction sooner, doesn't seem to do the trick (in my case)

kuworking

comment created time in 2 months

issue closedtimber/timber

How to pass the post.link property to JavaScript (when it is not available)?

I rephrase the question since it was wrong

I am trying to pass all posts information to a JavaScript variable, but I see that (at least) post.link is not available at that moment

Is there any strategy I could follow to pass all the Timber information?




OLD

Based on this https://github.com/timber/timber/issues/1434 I've seen why I wasn't getting my post.link attribute

However, I was using Timber starter, so I am wondering why isn't it used in the starter (?)

The starter, in index.php

$context['posts'] = new Timber\PostQuery();

Later, in index.twig

  {% for post in posts %}
    {% include ['tease-' ~ post.post_type ~ '.twig', 'tease.twig'] %}
    <script>
    var t = JSON.parse('{{post|json_encode(constant('JSON_HEX_APOS'))|e('js')}}')
    console.log(t)
</script>
  {% endfor %}

There is no link property in the array, probably because it is yet not injected there

If I write {{ post.link }} it appears, so I guess it is injected on demand only?

Then, if in the starter I use

$context['posts'] = Timber::get_posts();

Then the link is already included and present in the javascript object

I image this is on purpose, is it looking for speed?

closed time in 2 months

kuworking

issue commenttimber/timber

How to pass the post.link property to JavaScript (when it is not available)?

Absolutely, and sorry for the redundancy, now this makes complete sense :)

kuworking

comment created time in 2 months

issue openedtimber/timber

Timber starter uses PostQuery() instead of get_posts(), so .link property is not available, what's the reason?

Based on this https://github.com/timber/timber/issues/1434 I've seen why I wasn't getting my post.link attribute

However, I was using Timber starter, so I am wondering why isn't it used in the starter (?)

The starter, in index.php

$context['posts'] = new Timber\PostQuery();

Later, in index.twig

  {% for post in posts %}
    {% include ['tease-' ~ post.post_type ~ '.twig', 'tease.twig'] %}
    <script>
    var t = JSON.parse('{{post|json_encode(constant('JSON_HEX_APOS'))|e('js')}}')
    console.log(t)
</script>
  {% endfor %}

There is no link property in the array, probably because it is yet not injected there

If I write {{ post.link }} it appears, so I guess it is injected on demand only?

Then, if in the starter I use

$context['posts'] = Timber::get_posts();

Then the link is already included and present in the javascript object

I image this is on purpose, is it looking for speed?

created time in 2 months

issue commentgatsbyjs/gatsby

Worse performance results with Lighthouse v6 (?)

Is anyone addressing this? Seems like there is no point using Gatsby over Next if it doesn't deliver better scores out-the-box.

Do you have any numbers from Next? I am wondering whether these scores are the new normal for fast webs (that are not static, JS-free and likely also image-free)

A Next.js website -> https://masteringnextjs.com/ 77 mobile score. A lot of "Unused JS".

I see better scores with lighthouse-metrics https://lighthouse-metrics.com/one-time-tests/5edfbbb1cf858500080125f7

But I also don't see images there, and in my experience images seem to have a high (and legitimate IMO) impact

Yet, gatsbyjs.org neither has images and its score is (relatively) bad https://lighthouse-metrics.com/one-time-tests/5edfbc58cf858500080125ff (as compared with @cbdp example)

Let's see what gatsby devs think about this

kuworking

comment created time in 2 months

issue commentgatsbyjs/gatsby

Worse performance results with Lighthouse v6 (?)

Is anyone addressing this? Seems like there is no point using Gatsby over Next if it doesn't deliver better scores out-the-box.

Do you have any numbers from Next?

I am wondering whether these scores are the new normal for fast webs (that are not static, JS-free and likely also image-free)

kuworking

comment created time in 2 months

startedtrivago/prettier-plugin-twig-melody

started time in 2 months

startedmblode/vscode-twig-language-2

started time in 2 months

issue commentmblode/vscode-twig-language

Sorry, but there is no formatter for 'twig'-files installed?

Definitively it is not clear what should be installed, whether the two plugins or only one of them

In my case this has worked after restarting vscode and disabling the "other" twig extension (from whatwedo) (one of these two things solved the problem)

That said, wonderful and very needed extension, big thanks (!!)

keithmancuso

comment created time in 2 months

issue openedmdx-js/mdx

Include a component between ``` sections

If I want to add a repeated code within <pre><code> tags in my mdx component, I'd say this is not possible right now

export const Code = <div>......</div>

` ` `js
{Code]
` ` `

another time

` ` `js
{Code]
` ` `

and another time

` ` `js
{Code]
` ` `

So that if I want to repeat the code, I need to copy-paste the code in all places

If this is actually not possible, it would be a nice feature to add

created time in 2 months

issue commentgatsbyjs/gatsby

Ability to disable prefetching for certain links.

Perhaps use reach router link?

I worried about this while trying to optimize lightspeed scores, and at the end I've concluded that this link elements don't seem to affect the score

Still, I think would be nice to have a gatsby-option to just disable prefetching, or delay it, or anything, but as you say perhaps react link could work (don't know)

gc

comment created time in 2 months

issue commentdbeaver/dbeaver

IO Error: Utility 'mysqldump.exe' not found in client home 'MySQL Connector/Net'

Following what @dankkomcg said I have been able to start dumping the db (w10)

  • download mariadb server, extract and find mysqldump.exe
  • go to C:\Program Files\DBeaver\ and create the folder MySQL Binaries
  • copy-paste the previous exe file to that folder, and I've been able to start dumping my database

However, it seems to be frozen in this state without doing anything nor giving the change to finish the process (I ignore if this is related to the binary or it is another issue)

image

This works for me without installing any MySQL Server on w10 and using WSL:

  • Download the zip from your mysql version.
  • Go to C:\Users\{ YOUR USER }\AppData\Local\DBeaver
  • If doesn't exist, create into MySQL Binaries folder.
  • Open the zip and go to bin
  • Search mysqldump.exe and extract it into MySQL Binaries folder.
  • Try to export again.
levilogics

comment created time in 2 months

issue closedmdx-js/mdx

Variables cannot be checked in mdx

Provided that in a document I define a variable then I can use it as expected

export const special = 'because x'

This is a post that is special {special}

But if I want to check if special is defined, I can't

// export const special = 'because x'

<p>{special && `This is a post that is special ${special}`]</p>

At least it's giving me a ReferenceError, special is not defined

My use case is that I'm using a common mdx file for all posts, and I'd like to show a specific variable only if it is defined on the post

Is there any way to workaround this? Apart from defining the variable in all posts

closed time in 3 months

kuworking

issue commentmdx-js/mdx

Variables cannot be checked in mdx

Damn, you're right, I guess I'm never working with uninitialized variables 😓 Sorry for the disturbance

kuworking

comment created time in 3 months

issue commentmdx-js/mdx

Variables cannot be checked in mdx

I've found that I can workaround this with

<Comp
  special={typeof special !== 'undefined' ? special: null}
/>

That would suffice, leave it open in case I'm missing something here

kuworking

comment created time in 3 months

more