reggi

import {journey} from '@reggi/journey'
import * as lodash from 'lodash'

const getPairs = (obj) => lodash.entries(obj).map(([key, method], index) => ({key, method, index}));

const nestedReduce = (pairs, cb) => {
    return pairs.reduce((acq, fromPair) => {
        acq[fromPair.key] = pairs.reduce((acq, toPair) => {
            const r = cb({ fromPair, toPair });
            if (r) acq[toPair.key] = r;

reggi

const libs = []

export enum Types {
    number,
    numbers,
    string,
    buffer,
}

export enum Actions {

reggi

declare const lodash: typeof import('lodash')
export = lodash

reggi

enum Outing {
    COMEDY,
    DJ_DANCE_PARTY,
    SIT_DOWN_LIVE_MUSIC,
    BOARD_GAME_NIGHT,
    MOVIE,
    CONCERT,
    THEATER,
    DANCE_PROFORANCE,
    BILLIARDS,

reggi

Pacific/Apia  (GMT-11:00) Samoa Standard Time  (Apia) 
Pacific/Pago_Pago  (GMT-11:00) Samoa Standard Time  (Pago Pago) 
Pacific/Honolulu  (GMT-10:00) Hawaii-Aleutian Standard Time
America/Adak  (GMT-09:00) United States  (Adak) 
America/Anchorage  (GMT-08:00) Alaska Daylight Time
America/Ensenada  (GMT-08:00) Pacific Standard Time
America/Mazatlan  (GMT-07:00) Mountain Standard Time  (Mazatlan) 
America/Phoenix  (GMT-07:00) Mountain Standard Time  (Phoenix) 
America/Los_Angeles  (GMT-07:00) Pacific Daylight Time  (Los Angeles)
America/Vancouver  (GMT-07:00) Pacific Daylight Time  (Vancouver) 

reggi

var fs = require('fs')
var axios = require('axios')
var _ = require('lodash')
const bb = require('bluebird')
bb.promisifyAll(fs)

async function example () {
    const file = await fs.readFileAsync('./urls.txt','utf8')
    const urls = file.split('\n')
    const action = await bb.map(urls, async (url) => {

reggi

The idea is simple, all variables defined within a function are always returned and accessable outside of the function, no variables are ever "locked" inside a function.

* If it's called within a Prophesy the values declared within all Prophesys are retained in a shallow object.
* If it's called outside a Prophesy only the return property is returned.
* If there is no return property all properties are returned.
* Everything is maintained in a plain "Object". `{}`

```javascript
const add = new Prophesy((a, b) => [
  () => ({a, b}),

reggi

{
  "name": "abide",
  "version": "1.0.0",
  "description": "Collection of modules",
  "keywords": [],
  "license": "ISC",
  "author": "",
  "main": "index.js",
  "scripts": {
    "babel": "NODE_ENV=production lerna exec --parallel --bail=false -- npm run babel",

reggi

Hoping to not add to the noise, feel free to close.

In the example:

import { test } from "https://unpkg.com/deno_testing@0.0.5/testing.ts"
import { log } from "./util.ts"

The test function is pulled from a url that is cached. What happens if this test url also requires something from the file-system for instance ../meow.ts. Would it simply just keep following all the URLS and build the cache of everything that is on the given domain unless it runs into an error where a dep cannot be found? It would have to pull https://unpkg.com/meow.ts. I'd love to see a "sitemap" of all the dependencies download from all the given urls.

reggi

npm Versioning Bug

TLDR; this is about a specific versioning mishap that is happening with one of my packages. I have been in communication with npm about this issue since May 2nd.

Update: on May 7, 16:24 PDT I recieved this email from npm that this issue is a bug on their end.

I recently created a monorepo and I've been creating some small cli tools getting a feel for getting into open source at a larger scale so I've been publishing a lot of modules. I am having a rather complicated and odd npm issue and I wanted to document it.

The issue is with this package here @reggi/pkg.json-parse which many of my other packages depend on.