Christoph Werner

@code_punkt

Software Architect and web advocate • Organizer of • he/him

Paderborn, Germany
Vrijeme pridruživanja: studeni 2010.
Rođen/a 1981.

Tweetovi

Blokirali ste korisnika/cu @code_punkt

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @code_punkt

  1. proslijedio/la je Tweet
    2. velj

    Normally I might not re-tweet such a thing, but in this case, I find this valuable life information.

    Poništi
  2. proslijedio/la je Tweet
    31. sij

    📣 Just published: React Router v6.0.0-alpha.0 👀 - Relative routes + links - Nested routes ala v3 - Automatic route ranking - Suspense-ready navigation - Object-based route config with useRoutes Our most ambitious release since v4 🤘 Release notes 👇

    Prikaži ovu nit
    Poništi
  3. 30. sij

    folks: Why should i not do this? const [state, setState] = React.useState({ foo: 'bar' }) = 'baz' setState({ ...state })

    Poništi
  4. proslijedio/la je Tweet
    30. sij

    I've been doing some CSS inspecting of some pretty looking sites, focusing on content width. Genuinely surprised nobody seems to use the char unit, e.g. `max-width: 80ch`? Instead everybody seems to use pixels/%. Why? Isn't the normal advise to aim for 50-80 chars per line?

    Prikaži ovu nit
    Poništi
  5. proslijedio/la je Tweet
    17. pro 2019.

    The `git checkout` command was confusingly named and too overloaded in functionality. “How do I switch to a branch?” - checkout “How do I restore a file to a previous version?” - checkout Enter Git 2.23: - `git switch <branch>` - `git restore <file>`

    Prikaži ovu nit
    Poništi
  6. proslijedio/la je Tweet
    29. sij
    Odgovor korisniku/ci

    by is sooo much better with it's macros it's not even funny thinking about how much time people waste trying to wrap their html tags in a complex JSX spagetti soup.

    Poništi
  7. 29. sij

    I'm back at it and fixed a few errors that yarn threw at me by updating our deps and adding packageExtensions to .yarnrc.yml. Next in line is: A package is trying to access a peer dependency that should be provided by its direct ancestor but isn't What's way do i fix that?

    Prikaži ovu nit
    Poništi
  8. proslijedio/la je Tweet
    28. sij

    Thanks to and from for presenting at yesterday's meetup. Great presentation and live coding!

    Poništi
  9. 27. sij

    That's it for now folks. I will probably spend more time on this on wednesday. So far, everything went butter smooth and i'm looking forward to more yarn v2 adventures. Narrator: It was a strenuous endeveour and might still fail horrendously.

    Prikaži ovu nit
    Poništi
  10. 27. sij

    This could be a problem with the webpack plugin, that i might still be missing in the creat react app client application. I'm unsure about that because create-react-app 2.x is supposed to be supported? Or is it not?

    Prikaži ovu nit
    Poništi
  11. 27. sij

    After i've read that create-react-app starting from 2.x is supposed to support pnp resolution, i'm starting the development server with "yarn start" in the appropriate package subdirectory. Error: Couldn't find a suitable Node resolution for the specified unqualified path

    Prikaži ovu nit
    Poništi
  12. 27. sij

    After removing old lockfiles from the packages/* subdirectory, which was my bad because we didn't have yarn workspaces on this project to begin with, the error mentioned above is gone.

    Prikaži ovu nit
    Poništi
  13. 27. sij

    fsevents something could not be build, but other than that the node_modules are gone and the .yarn directory was filled. However, the error that some package doesn't seem to be present in my lockfile persists.

    Prikaži ovu nit
    Poništi
  14. 27. sij

    Installation of around 2500 dependencies is done. A few of them have automatically been unplugged (extracted) and right now the existing node_modules folders are removed.

    Prikaži ovu nit
    Poništi
  15. 27. sij

    Setting the local repositories yarn version to berry by running "yarn policies set-version berry" results in the same error. Interestingly enough, running a new install via "yarn" now seems to use the new version. Let's see what happens!

    Prikaži ovu nit
    Poništi
  16. 27. sij

    After v2 berry is installed globally, running "yarn pnpify --sdk" results in: Internal Error: @companyNamespace/portal@workspace:.: This package doesn't seem to be present in your lockfile; try to make an install to update your resolutions

    Prikaži ovu nit
    Poništi
  17. 27. sij

    Looks like yarn@berry has to installed globally first in order to use some pnp related code, so i just did that using: npm i -g @yarn/berry Little confusion about the namespaces here - some things are namespaced as , others as

    Prikaži ovu nit
    Poništi
  18. 27. sij

    What's up next is setting up our IDE, in this case vscode. To do so, i've added @yarnpkg/pnpify to the devDependencies (documentation omits the -D flag for unknown reasons) and ran "yarn pnpify --sdk" Error: Cannot find module 'pnpapi'

    Prikaži ovu nit
    Poništi
  19. 27. sij

    As we don't have any specific .yarnrc or .npmrc, i can gladly skip the step of updating the configuration settings there, but skimming over that part it seems understandable and well-documented.

    Prikaži ovu nit
    Poništi
  20. 27. sij

    Maybe i can just skip this step for now and will chime in later on. Next in migration guide: "Don't use resolve.alias|modules (Webpack) or moduleNameMapper (Jest)". Build/tooling config is abstracted away into packages not necessarily under my control, so i don't know.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·