kriasoft / kriasoft/node-pg-client

other approaches

Open
#1 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
16
Forks
0
PR merge metrics
No merged PRs in 30d

Description

I found within the large pool of projects based on pg-promise that when people want to use it with ES7 syntax, they just combine pg-promise with Babel, and that's it.

Some guidelines: http://stackoverflow.com/questions/33624104/how-do-i-setup-babel-6-with-node-js-to-use-es6-in-my-server-side-code

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points to inspect. Start by reading the proposed Babel 6 setup and comparing it with this package's current ES7 and build configuration; the intended change and a concrete definition of done still need to be established.

Written by the indexing model from the issue text.

Assessment

Tech stack
babel, javascript, node.js
Domain
backend, build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.