profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/trevorah/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Andy Trevorah trevorah London I like coffee as a treat

trevorah/backseat-writer 8

Words that complete themselves in the styles of different writers.

malditogeek/hook 3

Not a real repository.

AnthonyMann/nodecopterhackday 1

NodeCopter Hack Day

trevorah/boy-girl 1

Determines whether a name is a boys name or a girls name for node.js

kohola71/iOS-Goodies 0

Your favorite iOS Newsletter, now open source.

ticaboo/gitup 0

A node.js micro service that listens to GitHub web hooks, compiles gh-pages and manages meetup.com

trevorah/actionhero 0

actionhero.js is a multi-transport API Server with integrated cluster capabilites and delayed tasks

trevorah/ansible 0

Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy. Avoid writing scripts or custom code to deploy and update your applications— automate in a language that approaches plain English, using SSH, with no agents to install on remote systems.

PR opened vrunkel/F3XSwift

Fix typo
+1 -1

0 comment

1 changed file

pr created time in 2 months

push eventtrevorah/F3XSwift

Andy Trevorah

commit sha 76ebf1f51fb818dab65c2a45c0c10688573a1933

Fix typo

view details

push time in 2 months

fork trevorah/F3XSwift

macOS GUI to the f3 - Fight Flash Fraud - tool and based on F3X

fork in 2 months

pull request commentmeliorence/react-native-render-html

fix(types): fix ts error due to @native-html/css-processor dependency

I've tried to get a minimal reproducible example, but no dice. The project that has this strange node_modules layout is using yarn 1.22.4, so it's nothing too exotic. Oh, and typescript is plain 4.2.2.

I'm not sure why yarn would hoist these particular dependencies like so, maybe it was due to an upgrade from react-native-render-html v5 to v6 and yarn deciding to not shuffle dependencies around too much and avoid excessive yarn lock changes? Who knows. Either way, it is a valid node_modules setup chosen by yarn based on the dependency tree.

I could end up reexporting definitions from css-processor in transient-render-engine, to not import from css-processor in react-native-render-html.

That is probably the safest option.

trevorah

comment created time in 3 months

PR opened meliorence/react-native-render-html

fix(types): fix ts error due to @native-html/css-processor dependency

Checks

  • [x] I have read the contribution guidelines regarding Pull Requests here: https://git.io/JJ0Pg

Description

Bit of an odd one this. Typescript complains when using this package as @native-html/css-processor is unreachable from this package.

The dependency chain is like so:

react-native-render-html -> @native-html/transient-render-engine -> @native-html/css-processor

With a local npm/yarn install for this project, we a node_modules layout like so:

/packages/render-html
/node_modules
  /@native-html/transient-render-engine
  /@native-html/css-processor

But when a project uses it, we get something like so:

App.tsx
/node_modules
  /react-native-render-html
  /@native-html/transient-render-engine
    /node_modules
      /@native-html/css-processor

So ts complains as react-native-render-html cant access @native-html/css-processor directly.

This change fixes that by removing the direct access of @native-html/css-processor types and inferring them instead from @native-html/transient-render-engine.

+4 -8

0 comment

1 changed file

pr created time in 3 months

push eventtrevorah/react-native-render-html

Andy Trevorah

commit sha 38b9645cd2302699872d0124c60b55a344d59c5e

fix(types): fix ts error due to @native-html/css-processor transitive dependency Bit of an odd one this. Typescript complains when using this package as @native-html/css-processor is unreachable from this package. The dependency chain is like so: ``` react-native-render-html -> @native-html/transient-render-engine -> @native-html/css-processor ``` With a local npm/yarn install for this project, we a node_modules layout like so: ``` /packages/render-html /node_modules /@native-html/transient-render-engine /@native-html/css-processor ``` But when a project uses it, we get something like so: ``` App.tsx /node_modules /react-native-render-html /@native-html/transient-render-engine /node_modules /@native-html/css-processor ``` So ts complains as react-native-render-html cant access @native-html/css-processor directly. This change fixes that by removing the direct access of @native-html/css-processor types and inferring them instead from @native-html/transient-render-engine.

view details

push time in 3 months

fork trevorah/react-native-render-html

iOS/Android pure javascript react-native component that renders your HTML into 100% native views

https://meliorence.github.io/react-native-render-html/

fork in 3 months