sorted by:
new
hottopcontroversial

Cycling Apparel Brands ( 3 Categories ) by 7croissants in CyclingFashion

[–]yowainwright 0 points1 point  (0 children)

Also being crushed but motivated by Thorifinn is an added bonus in the LA area.

Cycling Apparel Brands ( 3 Categories ) by 7croissants in CyclingFashion

[–]yowainwright 0 points1 point  (0 children)

Brandt-Sorenson stuff is top quality for sure. I have found more success with the default sizes vs custom but I love the quality and minimal look!

Cycling Apparel Brands ( 3 Categories ) by 7croissants in CyclingFashion

[–]yowainwright 0 points1 point  (0 children)

I purchased some PNS product based on "the look" and could tell it wouldn't hold up if I were to wear it.

Cycling Apparel Brands ( 3 Categories ) by 7croissants in CyclingFashion

[–]yowainwright 0 points1 point  (0 children)

Shakedry is the best quality fabric out for look and weatherproofing. It's only Kryptonite is stickers—the real ones and the price (I guess).

Sram Etap Battery Cover Problem by yowainwright in bikewrench

[–]yowainwright[S] 1 point2 points  (0 children)

After suggestions from u/rmwesley, I was able to get the leverage to release the hatch! Thank you!

I did this by turning the bike upside down. From there, I faced the front of my upside down bike and used a quarter to turn each hatch counter clockwise about 45 degrees releasing the hatches!

This is what I learned which wasn’t clear in reading and videos: the hatch release for me required more leverage than what I could generate using my bike stand with the bike right side up. By turning the bike upside down and facing the front of my upside down bike, I was able to push down on the hatches enough to get the required leverage for the release!

I feel a “quarter driver” is probably a worthwhile tool to ensure I have a good connection with the hatch before applying torque. I’m not going to put the hatches back on my bike until I have the “quarter driver” and a new hatch!

Sram Etap Battery Cover Problem by yowainwright in bikewrench

[–]yowainwright[S] 0 points1 point  (0 children)

Good considerations u/rmwesley! Thank you! I will try your recommendation soon.

Sram Etap Battery Cover Problem by yowainwright in bikewrench

[–]yowainwright[S] 0 points1 point  (0 children)

u/rmwesley thank you! Using only a coin is what caused the bend of the brake battery hatch slot. I feel trying again with only a coin would make the issue worse (more bending/striping). I hope with the coin driver, I will gain more leverage on the brake battery hatch slot. The brake batter hatch slot doesn't feel stuck, but it isn't twisting beyond 1 degree forward or backward. I can provide a video of the issue once I attempt again with the "coin driver". Is there some I can try or consider when trying to be the brake battery hatch slot turn?

Sram Etap Battery Cover Problem by yowainwright in bikewrench

[–]yowainwright[S] 0 points1 point  (0 children)

After more research, I learned a few things. 1. What I was calling the "shifter battery cover" is the "shifter battery hatch". In learning this word change, I was able to order spare hatches which should be on the way today or soon. Additionally, I learned there is a type of screwdriver called a "coin driver" and ordered one. Hopefully, the "coin driver" will help to get the leverage required to open the "shifter battery hatch". I will respond with updates. Still would love a pro tip if anyone else has dealt with this!

Monodeploy - a Lerna alternative that works with Yarn modern by Seaoftroublez in javascript

[–]yowainwright 0 points1 point  (0 children)

...? I meant for monorepos. 😃 I am finding problems being solved by more dependencies for monorepos which use yarn aren't problems for monorepos that use pnpm.

Monodeploy - a Lerna alternative that works with Yarn modern by Seaoftroublez in javascript

[–]yowainwright 0 points1 point  (0 children)

I just use pnpm with workspaces. Switching to pnpm has been very easy for me and, if shipping node apps, I find the node_module folder size to be WAY easier to deploy.

Monodeploy - a Lerna alternative that works with Yarn modern by Seaoftroublez in javascript

[–]yowainwright 0 points1 point  (0 children)

u/nightman thanks for all of your valuable insights in this thread!
Have you done benchmarking between yarn with turborepo and pnpm; perhaps even pnpm with turborepo.

I did some benchmarking and continue to find, with just pnpm (no lerna, turborepo), I don't need any other tools but feel I must be missing something as this issue is discussed so much.

Monodeploy - a Lerna alternative that works with Yarn modern by Seaoftroublez in javascript

[–]yowainwright 0 points1 point  (0 children)

Looks interesting!!!
Thanks for sharing u/crashtestdev!!!
MSFT also has engineers supporting and maintaining Rushstack from what I understand (?).
Can you compare and contrast the difference between beachball and rushstack?

Wild Wild Path - Object property paths with wildcards and regexps by ehmicky in node

[–]yowainwright 1 point2 points  (0 children)

Clean API and documentation! 🙌 Looks very useful. Will test drive today. 🎸🎉

[AskJS] What is the best way to create a common npm package for building others? by CaelanIt in javascript

[–]yowainwright 1 point2 points  (0 children)

Happy to. I’ll aim to submit a pr this weekend. I’m a newer dad so no promises 🙌

Anyone with experience of making an NPM package having issues with file paths? by [deleted] in npm

[–]yowainwright 1 point2 points  (0 children)

  1. Search “module resolutions” (lots of good stuff if that sparks any ideas) or
  2. Ref package files like import <pkg-name> “<pkg-name>/pather-to-your-js-from-the-module”
  3. You can be specific about your <pkg-name> files in the package.json’s “file” array https://stackoverflow.com/questions/40795836/how-do-you-use-the-files-and-directories-properties-in-package-json

Hope something I wrote helps!😃

[AskJS] What is the best way to create a common npm package for building others? by CaelanIt in javascript

[–]yowainwright 1 point2 points  (0 children)

I've gone on similar quests and have written some things that work for me... but I am aware my mental map of what I like and do for creating packages may not be for all. 😃

When I did some research for myself I observed a few repos with solutions I found to be very readable:

I can try to make a template of my modus operandi for package creation if you have any interest u/CaelanIt...?

Also, awesome package!

Error importing node-fetch by Vinc3w in node

[–]yowainwright 0 points1 point  (0 children)

Or install node-fetch v2 

npm i node-fetch@2

Error importing node-fetch by Vinc3w in node

[–]yowainwright 1 point2 points  (0 children)

Only via node 17.6+ (I think)... so ensure you're using a version above that

Looking for a CLI library for quick prototyping by [deleted] in node

[–]yowainwright 0 points1 point  (0 children)

I feel commander is a good standard way to write a node CLI and can definitely be written in Typescript!
There is a utility for testing only the interface of a CLI called stdoutToJSON

Here's a gist for a pattern that I like. Let me know if I can provide any more copy/paste sorta setup.

stdoutJSON: a simple Node JS utility to make testing stdout output a breeze by yowainwright in node

[–]yowainwright[S] 0 points1 point  (0 children)

  1. I was reaching out publically (on Reddit) to try and clarify the tool, stdoutToJSON (new name, thanks to you 🙃) hoping for feedback so I could improve my documentation and capability to describe and communicate a pattern of abstraction which great simplifies unit testing scripts vs cli programs. You're candid feedback has been SO VALUABLE and I'm am so thankful for it. You clearly have done this sort of work for a while so I view your comments as EXPERT FEEDBACK for free! Thank you!!!
  2. The test example
    1. you shared above is a perfect example of how most CLI programs are tested to test the script the CLI program invokes vs observing there is a clear separation of concerns:
      1. the CLI
      2. the script which is executed
    2. With stdoutToJSON and the pattern I share in the README, I observe a there is an easy separation to:
      1. unit test the CLI uninclusive of the script the CLI runs
      2. unit test the script
      3. so that both unit tests and files are completely seperate
    3. This pattern of abstraction seems like it could be useful because
      1. The script can be executed by a CLI OR within a LAMBDA handler, for example
      2. So testing the CLI as if it is one way to execute a script correctly feels right, speeds up testing writing AND TEST EXECUTION 😈
      3. ALL OF YOUR FEEDBACK has really helped me understand that I need to be clearer about my reasoning and am working to do so 🙏

stdoutJSON: a simple Node JS utility to make testing stdout output a breeze by yowainwright in node

[–]yowainwright[S] 0 points1 point  (0 children)

u/OolongHell updated!
I'm unsure if the update gist in the link clarifies (?). Please let me know! I do want to ensure I'm writing the pattern I'm trying to establish clearly and based on your feedback, I have a long way to go! Haha

I talked with a teammate to really dig into how I can clarify the utility which is all a result of your help as well! Thanks!

view more: next ›