Anton Timmermans
Anton Timmermans
@coffee2code Did you do something specific on .org to fix this issue or was this fixed in the parser? Ping @DrewAPicture
Ah, so this is still an issue in the parser.
I think something like this should be in parser, maybe just very basic. Like just looping through all meta fields starting with "_wp-parser", unpacking the serialised values and displaying them....
I send @BoiteAWeb the export and he confirmed that he received it and could import it.
Completely support this, this would improve the decoupling between DevHub and WP-Parser as projects.
@anthonyshew It seems like there was already a code block for detecting the Yarn version. And somehow I put the change in the wrong one, oops. Because I wasn't able...
> Set Finicky as your default browser so it handles all links, but then get it to forward, by default, links to B: When I do this it indeed does...
This can easily be solved by changing the source of the content analysis to the description of the attachment.
> [Support ES module format (ESM) in next.config.js #32239](https://github.com/vercel/next.js/discussions/32239#discussioncomment-10948608) > > [@FleetAdmiralJakob](https://github.com/FleetAdmiralJakob) Yes, I get env checking during build with `import "./src/env"` > I can confirm that this also works...