Support for Alias HQ

[davestewart]

Hey @ilearnio,

I've just released a package called Alias HQ:

• https://github.com/davestewart/alias-hq/

It's an end-to-end solution for configuring, refactoring, maintaining and using path aliases.

Was doing some research on how to use aliases with Node, and this lib came up.

I've added it as a ticket to support this library:

• Add node plugin via module-alias package davestewart/alias-hq#9

That will be another way to solve #105, at least in the front end world.

If you have any thoughts, let me know!

[davestewart]

OK, this was super-easy and very meta!

As an experiment, I wanted to update Alias HQ to use aliases itself:

• I wrote an Alias HQ Node plugin to remap the Alias HQ Webpack plugin.
• I then used the Alias HQ CLI to convert all relative paths of Alias HQ itself.
• Finally:
  • I called the plugin
  • which calls your API
  • which allows Alias HQ to load itself... using aliases!

The plugin is this:

const moduleAlias = require('module-alias')
const webpack = require('../webpack')

module.exports = function (config, options) {
  const paths = webpack(config, options)
  Object.keys(paths).forEach(key => {
    moduleAlias.addAlias(key, paths[key])
  })
  return true
}

Implementation is this:

require('alias-hq').get('node')

[davestewart]

OK, have added support in v5.1:

• https://github.com/davestewart/alias-hq/blob/master/docs/integrations.md#node

The plugin integration is here:

• https://github.com/davestewart/alias-hq/blob/master/src/plugins/module-alias/index.js

Not sure if you want to mention it in your docs at all?

[Kehrlann]

Hey @davestewart , sorry, I've been quite busy lately ! Just wanted to let you know I'll take a look next week.

[davestewart]

Hey, no worries! I know what it's like trying to keep a hand on all the OSS projects. They are constantly asking for time you don't always have 😬