![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Start a new npm package with all the right tooling in place.
This package exposes the aberlaas
script that can be used to perform the most
common tasks on a package: build
, lint
, test
and release
. It also
exposes the inner configuration of the tools it uses.
Use this by calling the aberlaas
script to perform tasks on your code. The
following scripts
are automatically added to your package.json
.
"scripts": {
"build": "aberlaas build",
"build:watch": "aberlaas build --watch",
"lint": "aberlaas lint",
"lint:fix": "aberlaas lint --fix",
"test": "aberlaas test",
"test:watch": "aberlaas test --watch",
"release": "aberlaas release"
}
aberlaas build
will build all files located in ./lib
into ./build
by
default. You can alter the behavior with the following options:
aberlaas build ./path/to/files
to change the default source directory--out-dir ./dist
to change the destination directory--ignore ignore-me.js
to exclude some files--watch
to listen for changes on files and rebuildYou can extend the internal Babel by editing the .babelrc.js
created at the
root of your project.
Run aberlaas lint
to lint your files. You can call
aberlass lint ./your/own/files
to lint specific files. aberlaas lint:fix
will attempt to fix most errors.
All .js
files will go through ESLint. You can tweak the default configuration
by editing the .eslintrc.js
file created at the root of your project.
Run aberlaas test
to run all the Jest tests in ./lib
. You can pass your own
list of files to the command to override the default. Use the
--config jest.config.js
argument to specify your own config file and --watch
to start live reloading of test.
Run aberlaas release
to build the package and release it to npm. It will ask
your for the new version and will create the needed git tag. You can also run
aberlaas release patch
, aberlaas release minor
or aberlaas release major
to automatically bump the version number according to SemVer.
./lib/configs
contain the default configuration for all the tools. They are
exported by the package and thus can be import
ed in userland.
./templates
contains default configurations files copied to userland. Each
extends the configuration exported in the previous files. Copying files to
userland allows user to modify the files if they want to change the behavior.
.babelrc.js
, .eslintrc.js
, jest.config.js
and .huskyrc.js
are local
configuration files for aberlaas
itself. They eat their own dog food by
referencing the same configs as above.
Aberlaas is the base camp from which all great expedition start in the La Horde du Contrevent book. I felt it's a great name for a bootstrapping kit for modules.
FAQs
Scaffold your JavaScript projects with tests, lint and release scripts
The npm package aberlaas receives a total of 120 weekly downloads. As such, aberlaas popularity was classified as not popular.
We found that aberlaas demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.