benjamn / arson Goto Github PK

View Code? Open in Web Editor NEW

189.0 189.0 4.0 30 KB

Efficient encoder and decoder for arbitrary objects

License: MIT License

JavaScript 100.00%

arson's People

Contributors

Stargazers

Watchers

Forkers

manbaum norcoen shaibenyehuda japandmrp828forever2016

arson's Issues

Is this thing dead? (Request for maintainer rights)

This looks like an awesome lib that I'd love to use in one of my projects. However, there are a few things I'd like to see changed:

Port to TypeScript
Add Deno support
Add test coverage analysis tools, and property-based testing
Add performance benchmarking
See #4 merged
Add support for custom constructors so that library users are able to pass their own object constructors along with deconstruct and reconstruct functions
Experiment with storing object shapes in order to further reduce the size of the serisalised data (I have a use case where I serialise 10 almost identical objects but one small string deep inside changes, it would be great (but probably very hard) to reduce the redundancy here)

However, it looks like this project is no longer a priority for you. Are you willing to transfer this project to me so that I can take over and perform the changes I'd like to see?

If you disagree with the direction that I'd like to see this project take, that's fine. I can rewrite this in TS under a different name and credit your project for the excellent ideas it has.

I hope you have time to quickly respond. If I don't hear back from you, I'll just accept that this thing died and go my own way :)

Circular dependency when building with rollup

I had to comment out custom.js in order to package this up with rollup, as it seems like this circular dependency is not getting resolved correctly:

https://github.com/benjamn/arson/blob/master/custom.js#L11

Is there a way that we'd be able to reorganize the code to not make this a problem? Happy to submit a PR if we can come up with a solution.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

TypeScript signatures

declare module 'arson' {
  export type ARSONValue =
    | string
    | number
    | boolean
    | null
    | RegExp
    | Date
    | Buffer
    | Map<ARSONValue, ARSONValue>
    | Set<ARSONValue>
    | ARSONValue[]
    | { [key: string]: ARSONValue }

  type Serializer<S> = {
    parse: (x: string) => S
    stringify: (x: S) => string
  }

  export default Serializer<ARSONValue>
}

Buffer is not defined in browser (Chrome) environment

I'm trying to use Arson in Chrome (50.0.2661.94) and getting an error ReferenceError: Buffer is not defined when trying to stringify.

It seems that this line:

arson/custom.js

Line 11 in f9d522a

return Buffer.isBuffer(buf) && [buf.toString("base64"), "base64"];

assumes the presence of Buffer.

Not sure how to go about fixing this, since obviously a Buffer that is stringified in Node.js must have a different structure in the browser.

benjamn / arson Goto Github PK

arson's People

Contributors

Stargazers

Watchers

Forkers

arson's Issues

Is this thing dead? (Request for maintainer rights)

Circular dependency when building with rollup

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

TypeScript signatures

Buffer is not defined in browser (Chrome) environment

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent