Skip to content

Instantly share code, notes, and snippets.

View akoidan's full-sized avatar
👀
Looking for an employment

Andrew Koidan akoidan

👀
Looking for an employment
View GitHub Profile
@zyvpeople
zyvpeople / react-native-secure-storage+0.1.2.patch
Last active July 30, 2023 12:22
react-native-secure-storage@0.1.2 patch for react-native 0.68
diff --git a/node_modules/react-native-secure-storage/android/build.gradle b/node_modules/react-native-secure-storage/android/build.gradle
index fe7d65a..385272e 100644
--- a/node_modules/react-native-secure-storage/android/build.gradle
+++ b/node_modules/react-native-secure-storage/android/build.gradle
@@ -2,17 +2,19 @@
buildscript {
repositories {
jcenter()
+ mavenCentral()
+ mavenLocal()
@hfalucas
hfalucas / [1] main.js
Last active May 17, 2024 09:31
[Vue.js] Authentication and Authorization
/**
* Think of this "main.js" file as your application bootstrap.
*/
import Vue from 'vue'
import Resource from 'vue-resource'
import VueRouter from 'vue-router'
import routes from './routes'
import middleware from './middleware'
@branneman
branneman / better-nodejs-require-paths.md
Last active April 27, 2024 04:16
Better local require() paths for Node.js

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions