profile
viewpoint
Jerry Green JerryGreen https://jerrygreen.me Software Engineer, Full Stack

bithavoc/multilang-hstore 41

Multilang is a small library for translating database values for Rails 4 and Postgresql hstore

azer/indexeddb 30

Well-tested, low-level wrapper around the IndexedDB API. It can sync locally and remotely.

JerryGreen/git-pr 1

a helper script for git and github to create new / open existing PR for your branches

JerryGreen/bats 0

Bash Automated Testing System

JerryGreen/bracket_tree 0

Tree-based Bracketing System

JerryGreen/changes-notifier 0

Notification server for live clients that using PostgreSQL Pub/Sub, backend REST API and client Websockets

JerryGreen/chiliz 0

Сайт, показывающий чётная ли или нечётная неделя, числитель или знаменатель. Полезно для учебных заведений, студентов

JerryGreen/cocos2d-x_installing_tutorial 0

Cocos2d-x istalling guide

JerryGreen/create-preact-app 0

Create Preact apps with no build configuration.

create barnchJerryGreen/chiliz

branch : jerrygreen/upgrade-packages

created branch time in a day

issue commentzeit/now

Spec out new env system

@rauchg it might be more sense to keep this issue open while the functionality is not yet shipped to master branch

leo

comment created time in a day

startedjamiebuilds/the-super-tiny-compiler

started time in 5 days

issue openedbradleyboy/tuql

Does it work with indexeddb?

<!-- Sorry that this issue is more like QA, but I don't see how I may question otherwise. -->

indexeddb is meant to be SQLite replacement for web, it's literally a built-in SQLite, with the same types, etc. And I'm interested if this use-case was considered with tuql.

created time in 7 days

issue openedazer/indexeddb

select doesn't return promise

Currently I use a workaround, I made this function:

const storeSelect = (
  store: Store,
  indexName: string,
  rangeOptions: null | azerTypes.IRange,
  directionOrCallback?: string | azerTypes.ICallback,
  optionalCallback?: azerTypes.ICallback
): Promise<object[]> => {
  return new Promise(resolve => {
    const data: any[] = []
    const direction =
      typeof directionOrCallback === 'string' ? directionOrCallback : undefined
    const callbackRaw =
      optionalCallback ||
      (typeof directionOrCallback === 'function'
        ? directionOrCallback
        : undefined)
    const callback: ICallback = async (error, row: IDBCursorWithValue) => {
      if (error && callbackRaw) {
        callbackRaw(error)
      }
      if (row) {
        const value = row.value
        data.push(value)
        if (callbackRaw) {
          callbackRaw(undefined, row)
        } else {
          row.continue()
        }
      } else {
        resolve(data)
      }
    }

    store.select(indexName, rangeOptions, direction ? direction : callback)
  })
}

And here's how I use it:

const treeData = (await storeSelect(entityStore, "root", {
  only: "true"
})) as MyType[]

Not very related to the issue, but I don't really like the middle arguments are optional. This may seem convenient but it's anti-pattern, and there are two good other choices: either place optional arguments in the end, or (much better) use a single argument which is object, with some optional keys. Though, this workaround was used to almost mimic the original interface, so I didn't change it. In overall, btw, the library interface looks quite nice.

created time in 8 days

delete branch JerryGreen/chiliz

delete branch : timezone-fix

delete time in 8 days

push eventJerryGreen/chiliz

Jerry Green

commit sha 23bd699e8d7e5e54f57edab46ac30baf3e1b0783

Fix for timezones (#38) * Fix for wrong timezone, get local time only. Also remove unnecessary noreferrer * Fix a frozen chiliz

view details

push time in 8 days

PR merged JerryGreen/chiliz

Fix for timezones

Sun 15 Mar 2020, 01:34 - Числитель


Mon 16 Mar 2020, 23:00 - Числитель Fri 20 Mar 2020, 23:08 - Числитель


Tue 24 Mar 2020, 14:41 - Числитель

+29 -40

0 comment

5 changed files

JerryGreen

pr closed time in 8 days

push eventJerryGreen/chiliz

Jerry Green

commit sha 7271792f0ce0059f9267ff5d8ba41f0fa3f97468

Fix a frozen chiliz

view details

push time in 8 days

pull request commentzeit/next.js

Add support for paths in tsconfig.json and jsconfig.json

Wow, I was waiting for this feature! I like using ~/ alias for my src folder, and had to setup this in both next.config.js and tsconfig.json. Now one setting is enough. Thanks a lot!

timneutkens

comment created time in 9 days

pull request commentzeit/next.js

Add Layout prop for NextComponent

@timneutkens sorry, but can you link/say what upcoming changes do you mean, in particular? It should work with pure functions too, not just classes. And, btw, I could make a PR adding this functionality for layouts myself, it looks very straightforward (nor it's big change).

JerryGreen

comment created time in 12 days

issue openedreact-component/tree

Flat list data

I want to have flat list of objects, more like a relational database, rather than real tree. But it has all the info for the tree:

const treeDataList = [
  {
    key: '0-0',
    title: 'parent 1',
    children: ['0-0-0', '0-0-1'],
  },
  {
    key: '0-0-0',
    title: 'parent 1-1',
    children: ['0-0-0-0'],
  },
  { key: '0-0-0-0', title: 'parent 1-1-0' },
  {
    key: '0-0-1',
    title: 'parent 1-2',
    children: [
      '0-0-1-0',
      '0-0-1-1',
      '0-0-1-2',
      '0-0-1-3',
      '0-0-1-4',
      '0-0-1-5',
      '0-0-1-6',
      '0-0-1-7',
      '0-0-1-8',
      '0-0-1-9',
    ],
  },
  { key: '0-0-1-0', title: 'parent 1-2-0' },
  { key: '0-0-1-1', title: 'parent 1-2-1' },
  { key: '0-0-1-2', title: 'parent 1-2-2' },
  { key: '0-0-1-3', title: 'parent 1-2-3' },
  { key: '0-0-1-4', title: 'parent 1-2-4' },
  { key: '0-0-1-5', title: 'parent 1-2-5' },
  { key: '0-0-1-6', title: 'parent 1-2-6' },
  { key: '0-0-1-7', title: 'parent 1-2-7' },
  { key: '0-0-1-8', title: 'parent 1-2-8' },
  { key: '0-0-1-9', title: 'parent 1-2-9' },
]

Does rc-tree support such a flat shape? Ofc, I may make some additional layer myself, so original data will stay flat, but for the tree I'll have this additional layer which will be actual tree. But I'm wondering if it's already supported, because, well... It looks like a pretty much common case.

created time in 13 days

issue openedhashicorp/next-mdx-enhanced

Revalidate cache

Currently, the content of mdx files isn't hot reloaded, and you have to restart dev server to apply changes, - it would be more convenient to use

Though, btw, the tool is just great anyway!

created time in 15 days

issue commentmdx-js/mdx

Access FrontMatter datas Component MDX

There's great tool for extracting FrontMatter metadata, for NextJS: https://github.com/hashicorp/next-mdx-enhanced

MattMattC

comment created time in 15 days

issue commenthashicorp/next-mdx-enhanced

Element type is invalid

Huh! Just found an example of a simples layout in the README (was a little bit blind 😛):

export default frontMatter => {
  return ({ children: content }) => {
    return (
      <div>
        <h1>{frontMatter.title}</h1>
        {content}
      </div>
    )
  }
}

But then it turns out it's a little bit weird, because this layout isn't very compatible with regular pages, as mentioned here: https://github.com/hashicorp/next-mdx-enhanced/issues/16

JerryGreen

comment created time in 15 days

issue closedhashicorp/next-mdx-enhanced

Element type is invalid

I'm trying to make a simplest layout, to get this thing working. I have the following error:

Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

Screenshot

Screenshot 2020-03-17 at 13 58 15

My Code

Config:

// next.config.js
const { withPlugins } = require('next-compose-plugins')
const withMdxEnhanced = require('next-mdx-enhanced')

module.exports = withPlugins(
  [
    withMdxEnhanced({
      layoutPath: 'src/layouts/BlogLayout',
      defaultLayout: true,
      remarkPlugins: [],
      rehypePlugins: [],
    }),
  ],
  {}
)

Layout:

// src/layouts/BlogLayout/index.tsx
import { ReactElement } from 'react'

interface Props {
  children: ReactElement
}

const BlogLayout = ({ children }: Props) => {
  return (
    <div>
      {children}
    </div>
  )
}

export default BlogLayout 

closed time in 15 days

JerryGreen

issue openedhashicorp/next-mdx-enhanced

Element type is invalid

I'm trying to make a simplest layout, to get this thing working. I have the following error:

Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

Screenshot

Screenshot 2020-03-17 at 13 58 15

My Code

Config:

// next.config.js
module.exports = withPlugins(
  [
    withBundleAnalyzer,
    withCustomAliases({
      '~': resolve('src'),
    }),
    withMdxEnhanced({
      layoutPath: 'src/layouts/BlogLayout',
      defaultLayout: true,
      remarkPlugins: [],
      rehypePlugins: [],
    }),
  ],
  {}
)

Layout:

// src/layouts/BlogLayout/index.tsx
import { ReactElement } from 'react'

interface Props {
  children: ReactElement
}

const BlogLayout = ({ children }: Props) => {
  return (
    <div>
      {children}
    </div>
  )
}

export default BlogLayout 

created time in 15 days

startedhashicorp/next-mdx-enhanced

started time in 15 days

starteddworthen/js-yaml-front-matter

started time in 15 days

issue openedprimer/components

@primer/components has no exported member Grid

Screenshot 2020-03-17 at 11 11 37

P.S. I'm using 16.0.0 version of @primer/components

created time in 16 days

issue commentzeit/next.js

Truly static pages without react app

I believe what you want is Svelte. It's inspired by NextJS, and one of their main concerns is "No virtual DOM" and, overall, to move all the framework cycles into compile time, rather than runtime.

EugeneKostrikov

comment created time in 16 days

pull request commentzeit/next.js

Add Layout prop for NextComponent

@timneutkens yes, it's not part of the NextJS, but it's single sensible option to do layouting because in other ways your whole component tree is rerendered (and only with-dynamic-app-layout approach doesn't cause rerendering). There are some issues about layouting:

https://github.com/zeit/next.js/issues/8193 https://github.com/zeit/next.js/issues/9692 (dup) https://github.com/zeit/next.js/issues/9881 (dup)

And since it's pretty much common use case, to have layouts, and, among all examples, it's a single sensible way to do layouting, I thought it's also sensible to add this type.

Do you think it makes sense to include this Layout wrapper into native NextJS App component, so this won't be just a type for some example use case, but indeed will be a part of NextJS? So you won't be even required to make a custom _app? Like, official way to do layouting in NextJS.

JerryGreen

comment created time in 16 days

push eventJerryGreen/next.js

Jerry Green

commit sha 7f4e57f713e2fe258d532738bc8a09eb59cfe993

Add children argument to Layout props

view details

push time in 17 days

PR opened zeit/next.js

Reviewers
Add Layout prop for NextComponent

There's great example of layouting, though it assumes you have a Layout prop under Component:

https://github.com/zeit/next.js/blob/30cf4d5ab6b1665da2de322b6dbbc3f7b57216f9/examples/with-dynamic-app-layout/pages/_app.js#L4-L11

In TypeScript you'll get this error:

Screenshot 2020-03-16 at 04 44 54

This PR adds Layout as a potential prop. After the changes, it's now compatible with this example:

Screenshot 2020-03-16 at 05 08 45

+1 -0

0 comment

1 changed file

pr created time in 17 days

push eventJerryGreen/next.js

Jerry Green

commit sha 4f392623603ad8432ccb3eabc5d525a0035b94c2

Add Layout prop for Component

view details

push time in 17 days

create barnchJerryGreen/next.js

branch : layout-type

created branch time in 17 days

delete branch JerryGreen/next.js

delete branch : layout-type

delete time in 17 days

create barnchJerryGreen/next.js

branch : layout-type

created branch time in 17 days

delete branch JerryGreen/next.js

delete branch : layout-type

delete time in 17 days

PR opened JerryGreen/next.js

Add Layout prop for NextComponent
+0 -0

0 comment

0 changed file

pr created time in 17 days

push eventJerryGreen/next.js

Jerry Green

commit sha 9041d27f37d13083a7720baf8a0cfb59cef2c546

Starting a PR

view details

push time in 17 days

create barnchJerryGreen/next.js

branch : layout-type

created branch time in 17 days

push eventJerryGreen/next.js

Bee Ellis

commit sha d166840e5a2d10ec10dc40105f79f2de80a30c42

Fix shadowing of apolloClient (#9917) * Remove redefinition of apolloClient It seems that the definition of `apolloClient` on line 47 seems to be a intended to be defining the `apolloClient` defined in global scope. That re-declaration of the `apolloClient` variable is removed in favor of assigning the return of `initApolloClient()` to the globally defined `apolloClient` * Rename the global apollo client to globalApolloClient

view details

Vinci Rufus

commit sha 2e3a9720337055b9472ac618b3e82d4b32be5a26

Update the docker multistage to copy only the necessary files (#9899) * copy only the necessary files during stage 2 in multi-stage. * update readme

view details

JJ Kasper

commit sha 6e1762a751e44dd099583f2ced345a7505ebf55d

Remove extra logging from on-demand-entries (#9909) * Remove extra logging from on-demand-entries * Update on-demand-entry-handler.ts * Update on-demand-entry-handler.ts * Update on-demand-entry-handler.ts Co-authored-by: Tim Neutkens <tim@timneutkens.nl>

view details

Tim Neutkens

commit sha ed1424197c7d112cab52dc122282d51db3718a31

v9.1.7-canary.14

view details

Tim Neutkens

commit sha 9e9c7ea393c925f97f4a6bc7360e08da0d1fd781

Remove leftover symlink

view details

Tim Neutkens

commit sha 1546fcdcfd871cde1ffc0fce4ba9153c2786d0e2

Update contributing.md

view details

Tim Neutkens

commit sha c8799f9e7d1242ede62e16e3ce489e09d11525d7

Enable catchAllRouting by default (#9922)

view details

Tim Neutkens

commit sha 3a797f1a3879ebd9122dd91ba531c94335a81c86

v9.1.7-canary.15

view details

Igor Crispim Diniz

commit sha 2f1b15c6741c70c776dbb7d5f9373c4f86fe954f

Fix _app global css import order (#9836) * fix root components import order * import order tests * chunks attachment order tests

view details

Luis Alvarez D

commit sha fbcc0e818e9ea88f3b8d72b74b44890d47ec2ac7

😌 (#9923)

view details

Joe Haddad

commit sha 878ee56bb951ee020d3af41a770e20931fa124b4

Fix New CSS Support Media Paths (#9916) * Fix CSS Media Paths * update test * Use absolute path * Add new tests * fix import

view details

Sergio Xalambrí

commit sha 251f56b81f80c1740dd18bce038fcf42c77f9d60

Tailwind example only run PurgeCSS in production (#9846) * Tailwind example only run PurgeCSS in production * Apply lint Co-authored-by: Joe Haddad <timer150@gmail.com>

view details

Luis Alvarez D

commit sha d1fdd2bbf8df7e12f561f3eec0c1f16897502045

Add descriptions to documentation pages (#9901) * Added descriptions * Added descriptions to API Reference * Added descriptions to API Routes * Added descriptions to basic features * Added descriptions to the routing docs * Update exportPathMap.md Co-authored-by: Joe Haddad <timer150@gmail.com>

view details

Joe Haddad

commit sha a701072fc6f0c9e2b3e4b823d2432df980c971da

v9.1.7-canary.16

view details

Joe Haddad

commit sha 8e2ff2cd1f4c8ee401732ef2df425b34f383a239

v9.1.7

view details

Evgeniy Kumachev

commit sha ef6df482bfc05ffaaec6bd69b27728666bc55ad9

Add with-mobx-keystone-typescript example (#9844) * add with-mobx-keystone-typescript example * Use latest Next.js and removed gitignore * Fixed my suggestions * Enabled strict mode and simplified _app Co-authored-by: Luis Alvarez D. <luis@zeit.co>

view details

Joe Haddad

commit sha c4cf641c379a7dd506f553a16421b5524a764e49

Test 3rd Party CSS Modules (#9924)

view details

JJ Kasper

commit sha ae78e8f5be63617d575bab75f072d1feb62a292a

Fix get(Static|Initial)Props re-running when updating query (#9907) * Add failing test for re-calling getStaticProps after updating query * Fix get(Static|Initial)Props re-running when updating query * Update invalid export tests Co-authored-by: Joe Haddad <timer150@gmail.com>

view details

Cully Larson

commit sha 41d4084c040bd74b9519bb347fdfff7ce1f5c3a6

Add a missing word to the Static Optimization doc (#9926)

view details

Cully Larson

commit sha 4a7a28a887201b5eac527464543144fb54cd4b71

Fixup the Static HTML Export doc (#9928)

view details

push time in 17 days

issue commentstyled-system/styled-system

Order of applied css

Wait, "defaultProps are merged after the element's props" makes no sense. If default values can't be overridden, then they are not "default" values.

I'm facing the same problem with Flex, wanted to set justifyContent="flex-end", but default values (space-between) has higher precedence in output styles (I'm using Primer Components)

sktt

comment created time in 17 days

startedyou-dont-need/You-Dont-Need-GUI

started time in 24 days

startedyou-dont-need/You-Dont-Need-JavaScript

started time in 24 days

issue commentfacebook/react

Hooks don't work with yarn link

Workaround:

cd PACKAGE_YOU_DEBUG_LOCALLY
yarn link
yarn install
cd node_modules/react
yarn link
cd YOUR_PROJECT
yarn link PACKAGE_YOU_DEBUG_LOCALLY
yarn link react

I find it easier than some webpack setup or using yet another package manager (yapm? yanc? yalc? wut?)

andy9775

comment created time in a month

issue commentzeit/next.js

Adding GA script tag?

I'd say recommended way is to use this official example:

https://github.com/zeit/next.js/tree/canary/examples/with-google-analytics

It's already posted here. Sometimes I wish github issues to be more like stackoverflow, having some answer accepted and highlighted, right after the question (when there's too many messages and emojis is not enough. One option is to restrict commenting this post, so people will create a new issue instead. And while creating they'll find a similar issue was already created (thanks to "similar issues" feature), and it has an answer (but still, the answer with emojis is lost somewhere in the middle of long history, so it's not very convenient to find answers on github).

robinvdvleuten

comment created time in a month

issue commentmicrosoft/vscode

[npm] load description/homepage from referenced node module version

It looks pretty straightforward, so yes, I'll likely look into it on the weekend or so. Might be a first PR into vscode, why not make one :)

I'll leave a pair of links of related code for later:

https://github.com/microsoft/vscode/blob/531522b76e6f0c170f6933d7f1967cade9384ad5/extensions/npm/src/features/packageJSONContribution.ts#L251-L257

https://github.com/microsoft/vscode/blob/531522b76e6f0c170f6933d7f1967cade9384ad5/extensions/npm/src/features/packageJSONContribution.ts#L260-L280

JerryGreen

comment created time in a month

issue commentmicrosoft/vscode

Wrongly shows the repo of a package, when the source is github

@aechan yes, but it's incorrect to always use key as the source (i.e. npm). When the value starts with "github:", the source is github, not npm. By running npm install you'll find it installs from github.

JerryGreen

comment created time in a month

issue commentfortunejs/fortune-indexeddb

Add typescript definitions

@daliwali well, it's not needed for functioning, but it's needed to make all the codebase parts were clearly compliant to each other.

That's more like for Typescript fans. You'll probably be such a one too, later ;) And will find out why it's important on practice

JerryGreen

comment created time in a month

delete branch JerryGreen/graphql-genie

delete branch : fix-readme

delete time in a month

push eventJerryGreen/graphql-genie

Jerry Green

commit sha 3eee817736053c256f1793b3d1f02bdf0a496441

Update README.md - Fix missing import

view details

Jerry Green

commit sha e6bd6acf788c56fdd14cf151bc060b72f8564b96

Merge pull request #1 from JerryGreen/fix-readme Update README.md

view details

push time in a month

PR merged JerryGreen/graphql-genie

Update README.md
  • Fix missing import
+2 -1

0 comment

1 changed file

JerryGreen

pr closed time in a month

PR opened JerryGreen/graphql-genie

Update README.md
  • Fix missing import
+2 -1

0 comment

1 changed file

pr created time in a month

create barnchJerryGreen/graphql-genie

branch : fix-readme

created branch time in a month

fork JerryGreen/graphql-genie

Simply pass in your GraphQL type defintions and get a fully featured GraphQL API with referential integrity, inverse updates, subscriptions and role based access control that can be used client side or server side.

https://genie-team.github.io/graphql-genie-client/

fork in a month

issue openedfortunejs/fortune-indexeddb

Add typescript definitions

image

created time in a month

startedgenie-team/graphql-genie

started time in a month

startedgraphql/graphql-js

started time in a month

startedf/graphql.js

started time in a month

issue commentzeit/next.js

Client Side Rendering using Layouts without Reloading the entire page?

There are several examples of how to layout, but afaik this one does not cause root re-rendering:

https://github.com/zeit/next.js/tree/canary/examples/with-dynamic-app-layout

Little overview of the code:

https://github.com/zeit/next.js/blob/c57cdbb31de6143b86b9091afb8d4dc2a2f46cc5/examples/with-dynamic-app-layout/pages/_app.js#L6-L17

https://github.com/zeit/next.js/blob/c57cdbb31de6143b86b9091afb8d4dc2a2f46cc5/examples/with-dynamic-app-layout/pages/red.js#L6-L23

jfarris587

comment created time in a month

issue commentdenoland/deno

Deno.sh domain

Hey @ry, what do you think about using deno.sh, isn't it cooler, huh? Here’s person to donate this domain.

Maybe even consider it as main domain? You know, shell, sh, deno.sh.

JerryGreen

comment created time in a month

issue commentdenoland/deno

Deno.sh domain

Yea, I don't mean to force anyone. We are not like some russian police here, to privatise some businesses.

What I'm saying that this domain is IMO cool, and much cooler than deno.land. And yet, it's not used for anything useful (wrongly redirects to non-existing page).

I mean, did you even know "land" domain even existed before Deno? I always forget what's there after the dot and have to google it, rather to make a direct hit.

If Mu Shan is okay to giveaway domain, then it makes sense to maybe ask Ryan: "Hey Ryan, what do you think about using deno.sh, isn't it cooler, huh?" and maybe to use it as main domain.

JerryGreen

comment created time in a month

issue commentdenoland/deno

Deno.sh domain

Well, maybe it's a good idea to ask this guy... @zhmushan, is that your domain? Wanna donate it to Deno?

JerryGreen

comment created time in a month

issue openedmicrosoft/vscode

Wrongly shows the repo of a package, when the source is github

<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->

  • VSCode Version: 1.42.1
  • OS Version: macos Catalina 10.15.3

Steps to Reproduce:

  1. yarn add azer/indexeddb
  2. highlight indexeddb row in the `package.json

<!-- Launch with code --disable-extensions to check. --> Does this issue occur when all extensions are disabled?: Yes

Screenshot

Screenshot 2020-02-20 at 18 41 42

It shows https://github.com/bigeasy/indexeddb, though it should be https://github.com/azer/indexeddb

created time in a month

issue closedazer/indexeddb

Publish to npm?

The readme looks promising, especially the sync part (how granular is it, btw?). I think I'm going to try this thing.

But the main idea here: why not publish this to npm?

closed time in a month

JerryGreen

pull request commentazer/indexeddb

0.1.0

Cool, I've added 0.1.0 tag, so azer/indexeddb#0.1.0 works now!

Though it's still requires some manual manipulations, because yarn add doesn't add it by default, as it does for npm. I've created an issue there too:

https://github.com/yarnpkg/yarn/issues/7919

Gotcha about prova vs tape, btw. Thx!

JerryGreen

comment created time in a month

issue openedyarnpkg/yarn

Better github compatibility for adding dependencies

Currently, if I'll run yarn add azer/indexeddb, this will be added to my package.json as is:

"indexeddb": "azer/indexeddb"

I'd like to have yarn to automatically place latest git tag into my package.json, i.e.:

"indexeddb": "azer/indexeddb#0.1.0"

Currently this string is supported already. But the issue is about improving yarn add command, so I don't have to find and place the latest version number manually.

Some more context why I care at all (long story short: I care about semantic versioning):

https://github.com/azer/indexeddb/issues/2

created time in a month

created tagazer/indexeddb

tag0.1.0

Well-tested, low-level wrapper around the IndexedDB API. It can sync locally and remotely.

created time in a month

PR opened azer/indexeddb

0.1.0
+1 -1

0 comment

1 changed file

pr created time in a month

issue commentazer/indexeddb

Publish to npm?

@azer oh... Actually, I kinda hate npm too. Even author of NodeJS does kinda hate npm. Though, I'm not sure if the same thing won't ever happen for github...

But anyway my only worry here is probably different than just using npm. It's about versioning. For example, by running something like this: yarn add packagename I'll get something like this, in my package.json:

"packagename": "0.2.7",

I.e. package name, and the current latest version's digits. But when I do yarn add authorname/packagename, I'll get something like this:

"packagename": "authorname/packagename",

Which is nonsense. No version. When the package will be updated, it may be accidentally updated in the project, which leads to problems with having some working sets of libraries. Yes, - there's yarn.lock, listing a concrete commit anyway, but it's more like a cache rather than single source of truth, because sometimes it gets conflicts, is deleted, and recreated.

It's still possible to manually set it up in package.json:

"packagename": "authorname/packagename#a364c48",

But it has some commit hash, not a version, which is not very descriptive, though it's solves the problem.

So maybe I can't argue to using npm, but would you like to start at least 0.1.0 version (or even 0.0.1), and set a tag to this latest commit? So it will be possible to do this:

"packagename": "authorname/packagename#0.1.0",

or

"indexeddb": "azer/indexeddb#0.1.0",

rather than just:

"indexeddb": "azer/indexeddb",

And maybe I can even assure you to use this semantic versioning for all your libraries? It has nothing to do with npm, but it's still a useful practice. I'm not sure if git tags are transferred within PRs, but I'll make a PR to check it out.

Thanks for your reply, and thanks for listening! You look like a real cool guy, I've subscribed to your blog like a day ago, when found your lib.

JerryGreen

comment created time in a month

created tagJerryGreen/indexeddb

tag0.1.0

Well-tested, low-level wrapper around the IndexedDB API. It can sync locally and remotely.

created time in a month

push eventJerryGreen/indexeddb

Jerry Green

commit sha e9938ad8548385148433218d94c9472d0368d619

0.1.0

view details

push time in a month

fork JerryGreen/indexeddb

Well-tested, low-level wrapper around the IndexedDB API. It can sync locally and remotely.

fork in a month

issue openeddenoland/deno

Deno.sh domain

Isn't it your guys domain? I'm pretty much sure it was mentioned somewhere, maybe in youtube vids or something, at very starting point, but now it leads to some non-existing repo:

https://github.com/zhmushan/deno.sh

Funny fact: it's has higher priority in my browser than deno.land lol (I know I may clear the history regarding deno.sh, so it's not what's the issue about).

Maybe it's good idea to setup redirection of deno.sh to deno.land.

Though I, personally, think deno.sh name is better than deno.land. Though, "deno land" may sound pretty funny, but deno.sh sounds more relevant since it's shell command (like now.sh, - they are also using this name in vids etc, though it's redirected to zeit.co).

Btw, I don't want to force anyone to using it or whatever, I'm pretty much hate the situation of top level domains. Just asking...

created time in a month

issue openedazer/indexeddb

Publish to npm?

The readme looks promising, especially the sync part (how granular is it, btw?). I think I'm going to try this thing.

But the main idea here: why not publish this to npm?

created time in a month

startedazer/indexeddb

started time in a month

issue openedbradleyboy/tuql

Only CLI option?

I'd like to import the lib from my js/ts file, with some of my own logic, and start the server from there like:

import { createServer } from 'tuql'

created time in a month

issue commentdenoland/deno

Wanted: serverless deno configuration

@josermorales huh, thx... And this one looks particularly cool (haven't tried it yet though):

https://github.com/lucacasonato/now-deno

// now.json
{
  "functions": {
    "api/**/*.{j,t}s": {
      "runtime": "now-deno@0.3.0"
    }
  }
}
// api/hello.ts
import { APIGatewayProxyEvent, APIGatewayProxyResult, Context } from 'https://deno.land/x/lambda/mod.ts';

export async function handler(
  event: APIGatewayProxyEvent,
  context: Context
): Promise<APIGatewayProxyResult> {
  return {
    statusCode: 200,
    body: `Welcome to deno ${Deno.version.deno} 🦕`,
    headers: {
      'content-type': 'text/html; charset=utf-8',
    },
  };
}
ry

comment created time in a month

startedhayd/deno-lambda

started time in a month

startedlucacasonato/now-deno

started time in a month

PR opened JerryGreen/chiliz

Fix for timezones
+29 -40

0 comment

5 changed files

pr created time in a month

create barnchJerryGreen/chiliz

branch : timezone-fix

created branch time in 2 months

startedprimer/octicons

started time in 2 months

issue openedgragland/usehooks

Publish to npm?

These hooks look cool, but did you consider publishing them to npm as libraries? So it will be possible to update dependencies, instead of having a constant copy inside our own repo?

P.S. The only important note here I'd like to mention, - to make possible to use these type of imports:

import useAuth from 'usehooks/useAuth'

Rather than:

import { useAuth } from 'usehooks'

Afaik, tools like NextJS optimize their buindles based on from values. I.e. by describing:

from 'usehooks/useAuth'

It will bundle only this useAuth part and its dependencies, rather than whole usehooks library.

P.P.S. npmjs.com/usehooks is free for now btw

created time in 2 months

issue commentsaltyshiomix/nextron

How to deploy with `now.sh`?

@lacymorrow yea, it wasn't very obvious of how to make it work in both web and electron. I have a pair of ideas of how to make this more friendly:

  1. Use rendererSrcDir: '.' by default
  2. Move pages to src/pages
  3. Move main to src/electron-main (this may break things a bit)
  4. Encapsulate my withElectron function into nextron, so I may: const { withElectron } = require('nextron')
  5. Add "now-build": "WEB=true next build" hint into this repo readme

Also, potential number 6: I'm not sure about "postinstall": "electron-builder install-app-deps", - currently, it's executed inside Zeit Now deployments too because it has to, but this looks like a requirement for just electron, not the web. To make sure, I've tried to remove it, and the web version is still working with no problems. So it's probably a bad place for postinstall, and better to include it into nextron cli instead.

If anyone started a PR, I may probably help to settle it all down, if it's needed.

JerryGreen

comment created time in 2 months

issue commentsveltejs/svelte

Working TS compiler & AST type checker

Yea, one of my main concerns about Svelte, - it's overloaded with some template code out of the box. It was mentioned many times that Svelte is inspired by NextJS many times. Though, if you'll create NextJS project:

npx create-next-app

You'll get a fine structured folder, with a few code dependencies in package.json, with just 2 example pages [you'll later replace], and no any configs at all.

Though, if you'll want to create a Svelte project...

npx degit sveltejs/template my-svelte-project

I could already notice "what is this degit?", and why can't I use just npx create-svelte-app? But it's not my real concern here...

And what do I get in a newly created project? Yes, a similar example page, which I will replace with my real page, but what else?.. Rollup config? Some main.js? And also... A README.md with a hundred lines, which also asks me to run npx degit sveltejs/template svelte-app, srsly?

And, for the sake of justice, I admit, - it's already much better than it was months (a year?) ago. Earlier, there was also a service-worker.js... Btw, I hope it's not just "removed" now, but encapsulated somewhere?

For typescript support you'll also need tsconfig.json, - which is okay (ideally, to extend it from the library???), but if it will also require some additional configs like some another more complex rollup config, some library types within a project, etc., - then it will make the "no config" situation even worse. If I create a new project, and it's overloaded with tons of configs right from the start, - it's only part of the issue that your mind is overloaded too, but another issue, - you won't get updates regarding changes to these configs. I.e. if there will be some changes in svelte, for initial rollup config, tsconfig, etc., - then, because they are part of the project, not a part of the library itself, you will have to change them manually upon library updating.

Best practices, anyone?

So in our programming world we have this good practice of having no configs required. A good practice of having default values. A good practice of conventions over configurations. A good practice of encapsulations. And by breaking these laws, it brings a lot of frustration when one uses such instruments.

And I suppose it's very important thing here in this issue, "no configs", - that what it means "to have first-class typescript support". Otherwise it's not first class, - maybe some economy class, having you to say: "yes, we support typescript but...".

Yet, don't get me wrong, - a lot of guys here did real good work toward typescript support here. This TS-based compiler, and this tutorial rewrite... I really appreciate your guys work, and willingness to use typescript, - I like typescript too! I just point to important problems I see with these typescript template repositories some of you share here. I understand "then do it yourself" concept, I'm just not ready to. Currently, pointing to where's the problem is much easier for me than implementing a solution here, - it's real hard, and that's why I so much appreciate your guys work here! I hope, I helped someone to see things a bit clearer. Thx for attention.

marcus-sa

comment created time in 2 months

startedtem-tem/faunadb-test

started time in 2 months

startedgoogle/schema-dts

started time in 2 months

fork JerryGreen/nextron

⚡ Electron + NEXT.js ⚡

https://npm.im/nextron

fork in 2 months

issue closedsaltyshiomix/nextron

How to deploy with `now.sh`?

How to properly deploy the application with now.sh?

I mean, I want to have both types of application:

  1. in an electron wrapper
  2. and as a web service

My main concern is how to handle renderer path properly. Looks like I need some config like:

// now.json
{
  "version": 2,
  "builds": [{ "src": "renderer/package.json", "use": "@now/next" }]
}

But this brings a lot of mess with paths, requires a symlinked package.json, and I think maybe there's simpler way...

closed time in 2 months

JerryGreen

issue commentsaltyshiomix/nextron

How to deploy with `now.sh`?

I've found it's possible to pass a nextron config, like:

// nextron.config.js
module.exports = {
  rendererSrcDir: '.',
}

So since my NextJS code in my root now, it's as easy to deploy as before. Though, it'll require additional workaround in package.json:

"now-build": "WEB=true next build",

And something like this:

const { WEB } = process.env

const withElectron = previousNextConfig => ({
  ...previousNextConfig,
  webpack(previousWebpackConfig, options) {
    const webpackConfig = {
      ...previousWebpackConfig,
      target: WEB === 'true' ? undefined : 'electron-renderer',
    }
    return buildWebpackConfig(previousNextConfig, webpackConfig, options)
  },
})

module.exports = withElectron()

Still, much easier than mess with renderer folder.

JerryGreen

comment created time in 2 months

issue openedsaltyshiomix/nextron

How to deploy with `now.sh`?

How to properly deploy the application with now.sh?

I mean, I want to have both types of application:

  1. in an electron wrapper
  2. and as a web service

My main concern is how to handle renderer path properly. Looks like I need some config like:

// now.json
{
  "version": 2,
  "builds": [{ "src": "renderer/package.json", "use": "@now/next" }]
}

But this brings a lot of mess with paths, requires a symlinked package.json, and I think maybe there's simpler way...

created time in 2 months

issue openedsaltyshiomix/nextron

Why so weird separation between dependencies and devDependencies?

https://github.com/saltyshiomix/nextron/blob/0d036e6a2408b31c88ff806ade51b057a2f2795c/examples/api-routes/package.json#L13-L25

Even next, react, react-dom in devDependencies? Shouldn't they be in dependencies? Am I misunderstanding something?

created time in 2 months

issue closedJerryGreen/chiliz

Local MD files option

So the content is stored within the repository where the library is used

closed time in 2 months

JerryGreen

issue commentJerryGreen/chiliz

Local MD files option

(whoops wrong repo lol)

JerryGreen

comment created time in 2 months

issue openedJerryGreen/chiliz

Local MD files option

So the content is stored within the repository where the library is used

created time in 2 months

issue openedJerryGreen/chiliz

Improve analytics

https://github.com/zeit/next.js/tree/canary/examples/with-google-analytics

created time in 2 months

issue closedbeakerbrowser/beaker

Tabs stuck in a blank screen

Problem

Sometimes tabs don't show any info, and cannot be closed. It happens with various pages, including some of dat: pages, but the most easy reproducible way to achieve it what I've found is to open Settings, - it never opens.

Preview

Untitled

Versions

Operation System: macOS Catalina 10.15.2 Beaker version: 0.8.8

closed time in 2 months

JerryGreen

issue commentbeakerbrowser/beaker

Tabs stuck in a blank screen

Huh, it's indeed a duplicate. I'll close this issue, and will subscribe to that one :)

JerryGreen

comment created time in 2 months

startedfauna/faunadb-zeit-sample-app

started time in 2 months

startedpikapkg/snowpack

started time in 2 months

issue closedJerryGreen/chiliz

to make nvm automatically apply required node

using package.json and some of these hacks:

  • https://stackoverflow.com/a/36553730/3720305 source $HOME/.nvm/nvm.sh; nvm use
  • https://github.com/creationix/nvm/issues/651#issuecomment-241067305 use package.json engines.node to generate .nvmrc

closed time in 2 months

JerryGreen

issue commentJerryGreen/chiliz

to make nvm automatically apply required node

There's VSCode extension for that:

https://marketplace.visualstudio.com/items?itemName=abumalick.vscode-nvm

JerryGreen

comment created time in 2 months

issue closedsaltyshiomix/nextron

ReferenceError: Can't find variable: require

This example works in electron, but it's broken when I open localhost:8888/home in browser. I see the following error in devtools console:

ReferenceError: Can't find variable: require

closed time in 2 months

JerryGreen

issue commentsaltyshiomix/nextron

ReferenceError: Can't find variable: require

@saltyshiomix huh, just checked it, it indeed works. So it's a question of optimization... Thank you for your feedback!

JerryGreen

comment created time in 2 months

more