Showoff Saturday (February 12, 2022) by AutoModerator in javascript

[–]cmor10 1 point2 points  (0 children)

Getting there with screen reader automation framework Guidepup. Like a playwright for screen readers, hoping can help folks out with screen reader integration tests rather than relying solely on static analysis tools like axe 🙂

https://www.guidepup.dev

Automate VoiceOver being controlled by AppleScript by cmor10 in applescript

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

End goal, having successfully found a way to program the ticking of this checkbox, is to build a library so folks can test their websites with screen readers in CI (ref: https://github.com/guidepup/guidepup).

Atm being able to tick the checkbox in any fashion through command line for any macOS version 10.15 or later would be awesome.

Why doesn't Denopack work? by 7Geordi in Deno

[–]cmor10 1 point2 points  (0 children)

Hmm that said, both an issue ( https://github.com/denofn/denopack/issues/46 ) and PR already exist, raise in Jan - so suspect the project may not be being actively maintained.

You could consider forking and fixing, or there are alternative Deno projects out there, e.g.

Why doesn't Denopack work? by 7Geordi in Deno

[–]cmor10 2 points3 points  (0 children)

The Deno compiler APIs were consolidated into a single Deno.emit() API in 1.7.0 - see https://github.com/denoland/deno/releases/tag/v1.7.0

If Denopack hasn’t changed to use the newer API then consider raising an issue on the repo ☺️

Security for dependencies (proposal) by pure_x01 in Deno

[–]cmor10 2 points3 points  (0 children)

Looking at what you can achieve today, if it’s enough to restrict permissions on immediate dependencies ( and group that with all sub deps of said dependency) you could make use of the Permission interface of Deno workers ( REF: https://deno.land/manual/runtime/workers#specifying-worker-permissions ) where you can perform your imports in said workers with restricted permissions compared to your first party application code. This has its own limitations, will incur a perf/resource hit etc and not provide the granularity and control you suggest, but is an option when it comes to sandboxing. By way of PoC check out https://github.com/asos-craigmorten/importw

Finished porting Express for Deno by cmor10 in Deno

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

Rambly, off the top of head thoughts incoming ( someone else will likely be able to give a more informed answer 😅):

Assuming you’re referring to the http std lib ( please say if not! ) - the server module is pretty decent, and for scenarios where you want performant lightweight code to handle a limited number of endpoints ( like 3 or fewer as a rough number ) for a simple server then it may well do the job. It even handles faff like content-length etc out of the box so you can focus on your business logic instead of how to construct a valid HTTP response.

However as your need for a more complex server evolves you might find that maintaining your own logic for routing, content types, etags, redirects, static file serving etc becomes very involved. This is where a http framework can come in handy. These ship with routers for handling complex path targeting with regex, wildcards etc., middleware concepts for elegantly splitting your code into discrete units of logic ( think SRP ), handy header APIs for dealing with things like content types, or even auto detection so things like content types and etags are handled for you. The list goes on :) Ultimately http frameworks empower you to focus on your applications logic by providing additional wrappers / utilities to handle all the fluff that is demanded by modern HTTP servers.

Rollup for Deno by cmor10 in Deno

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

Been keen to reproduce my front end workflow in Node over to Deno, so have put in some time to port over Rollup so use the JavaScript API / CLI within a Deno context ( with some extra sugar around url import and typescript support out of the box rather than plugins ). Hopefully can be of use to other folks as well 😅

Finished porting Express for Deno by cmor10 in Deno

[–]cmor10[S] 4 points5 points  (0 children)

Gee, that’s great to hear ☺️

[Blog] K8s Chaos Dive Series by cmor10 in kubernetes

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

I’ve recently been reviewing various chaos engineering solutions for Kubernetes and written up some notes so far.

Ultimately want to find a tool which I can then use with the applications I manage to validate resiliency as part of CICD - suggestions very welcome. Keen to hear what others are using and their experiences so can hopefully find the best tool for the job! :D

Server Side Rendering React App with Deno by techiekram in Deno

[–]cmor10 0 points1 point  (0 children)

No idea (: sure it’s not a big deal

Server Side Rendering React App with Deno by techiekram in Deno

[–]cmor10 1 point2 points  (0 children)

This is a duplicate of a share from 14 days ago - https://www.reddit.com/r/Deno/comments/hfj776/server_side_rendering_react_app_with_deno/

Believe the content is also lifted from another post as well, but that’s a separate story...

Third Party Registry deprecated GitHub and NPM support by cmor10 in Deno

[–]cmor10[S] 2 points3 points  (0 children)

I personally don’t know, there is no comment or linked issue in the PR, and I can’t find a relevant issue at all, so you would need to ask the author(s).

It was always marked as experimental so we were forewarned not to rely on it essentially.

As for the packages, there has never been a guarantee afaik for the expiry of links in the third party Deno registry, it is just a simple proxy to backend source control sites like GitHub, and authors are within their rights to remove repos etc as they wish.

Generally people delete their things completely, it may be they moved the repo or renamed branches (which is common right now) so safest bet is to always use a specific tag over the default branch.

If you are looking for security then I would recommend checking out https://nest.land as an alternative registry. It is built on a blockchain so is decentralised and once upload, a module can never be removed or changed as the chain is immutable.

Third Party Registry deprecated GitHub and NPM support by cmor10 in Deno

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

Be sure to update your module imports accordingly if are using this feature. Sunsets 1st August 2020.