![Introducing Enhanced Alert Actions and Triage Functionality](https://cdn.sanity.io/images/cgdhsj6q/production/fe71306d515f85de6139b46745ea7180362324f0-2530x946.png?w=800&fit=max&auto=format)
Product
Introducing Enhanced Alert Actions and Triage Functionality
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
babel-compile
Advanced tools
Readme
While putting static babel-compiling in place, we've discovered that the babel
cli client is not perfectly suited to our usage. We can only compile by directory
one at a time, we have to wrap our babel invocations in an rm -rf out/
to make
sure that only files we expect to exist do. Instead of trying to fix the upstream
cli client, we've decided to use the really simple babel-core API to do our compiling
ourselves.
The result is a babel cli client which does things the way we want:
First, you're going to want to install this package and the taskcluster global configs
npm install babel-compile --save-dev
npm install taskcluster-configs --save-dev
Next, you're going to want to add it to your package.json
file's scripts
section.
Assuming that you store your code in src/
and your tests in test/
and you
want them to respectively end up in lib/
and .test/
, you could add the
following to your package.json:
...
"scripts": {
"compile": "babel-compile -c taskcluster-lib-rules/babel src:lib test:.test",
"pretest": "npm run compile",
"prepublish": "npm run compile"
}
...
Whenever you run npm test
or npm publish
, you will also have your code compiled
automatically. If you want to test your code, you can run npm run compile
to get
a compiled copy.
Mocha has a built in hook for comping code with babel as its imported. We
don't use this hook anymore as it could work around bugs correctly in tests
that aren't worked around in a deployed set of code. An example of problem
code is the Array.prototype
shim methods like .include
.
When importing code from a babel-compiled library in your tests, ensure that you
require('../lib/file');
to include the compiled copy for the program.
As well, your package.json file's test script should use, as an example,
.test/*_test.js
instead of test/*_test.js
If you're using Node 0.12, you're likely noticing that your stack traces are terrible. This is because the Node 0.12 environment doesn't support source maps natively. If you'd like to have useful stacktraces, you can do this:
npm install source-map-support
and then, in your non-library js-code, add
require('source-map-support').install();
to get nice stacks with real line numbers. More details here: https://github.com/evanw/node-source-map-support
FAQs
A script to compile .js and .jsx to es6 with Babel using babel-core, that actually works!
The npm package babel-compile receives a total of 38 weekly downloads. As such, babel-compile popularity was classified as not popular.
We found that babel-compile demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.