Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: xdpm should provide command to output installed directory #8

Open
tato123 opened this issue Nov 13, 2018 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@tato123
Copy link

tato123 commented Nov 13, 2018

xdpm provides a mechanism for developers to sync their code against the development folder. However for plugins that use npm packages this means building your package with a third party tool (like rollup, webpack, or parcel) and then executing xdpm as a second command or running a second tab to run the watcher.

This effectively doubles the number of watchers (one for the package tool and one for xdpm).

I'd like to propose adding a where command that only outputs the developer install directory (which may be different than running other npm modules that expose where,which, or locate).

The command xdpm where should only output a directory:

Example:
<<adobe xd install>>/develop

which can then be passed to cli commands as an output directory

OR

The command should be usable from within a script (for use with rollup, webpack, parcel, etc...) like so:

const xdWhere = require('@adobe/xdpm/commands/where');
const path = require('path');

module.exports =  {
  entry: 'main.js',
  output: path.resolve(xdWhere(), 'main.js'),
  plugins: [
    copyPlugin(['.json'])
  ]
}

This enables developers to quickly get started when using npm (or even transpiling)

@kerrishotts
Copy link
Contributor

Thanks for the suggestion.

This makes me think that exporting most of XDPM's functionality so that it could be scripted from other modules would be a good idea. If it exported the XD develop folder location, that'd serve your particular need, but having an exported API for installation, packaging, etc., could also make integration easier with other tools.

@kerrishotts kerrishotts self-assigned this Nov 15, 2018
@kerrishotts kerrishotts added the enhancement New feature or request label Nov 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants