We plan to gradually migrate brain.js to TypeScript, code base is pretty large, so we would love your help! 💪

How to contribute?

• Convert a file from .js to .ts
• Add types, fix all type errors.
• Submit a PR! 🎉

Here you can find a guide on how to contribute.

Want to convert something, let us know in the comment an

Starting from version 12.12.0, Node.js offers built-in support for translating error stack traces using source maps - learn more here: https://medium.com/@nodejs/source-maps-in-node-js-482872b56116

Let's rework @loopback/build to use this new feature on recent version of Node.js, instead of source-map-support module.

If it's possible, then implement a fallback to npm module `source-map-s

We loved caniuse-db, but it uses 7 MB and contains many irrelevant data.

This is why @ben-eb created caniuse-lite. It is just a copy of latest caniuse-db (he wrote autorelease script) with less data and better compression. Only 1 MB.

Autoprefixer and Browserslist moved to caniuse-lite. So let’s use it here too. It is very easy, API is the sam

Name of Issue

GET request of schema inputs throw error.
Workaround is to use POST or write middleware (example below)

• ActionHero Version: 16.0.5
• Node.js Version: 7.4.0
• Operating System OSX

Steps to reproduce your error

• Make a new actionhero project with ./node_modules/.bin/actionhero generate

./node_modules/.bin/actionhero generate action --name="schemaTest" 

Is your feature request related to a problem? Please describe.
When importing a file, some labels are skipped but without knowing which ones

Describe the solution you'd like
At the end of the import, have the list of skipped labels (and as a bonus, the reason)

FoalTS documentation is awesome. It helps me building a good grasp of how a framework takes care of auth, orm, cli, etc. step by step thru Tutorials and Topic Guides.

If it's possible, I'd love to translate it — to Bahasa Indonesia. Hope v2 is a good starting point.

What do you think?

Current version is 1.0.1

The current getting started guide assumes the user will be starting using the SDK building block packages like tracing, node, and metrics. In the future, it is expected most users will use the SDK package as a starting point and it would be better for the getting started guide to reflect that.