You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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 exposewhere
,which
, orlocate
).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:
This enables developers to quickly get started when using npm (or even transpiling)
The text was updated successfully, but these errors were encountered: