Consider separating CLI. about speedline HOT 6 CLOSED

Yeah. This would be quite straightforward to do, as well.
I suppose the only question is... do we want to retain git history for cli.js?

from speedline.

looks like we can do it :)
http://gbayer.com/development/moving-files-from-one-git-repository-to-another-preserving-history/

from speedline.

Hi, old task. I have started to split console client and the lib. You can mark this issue "in progress"

Job is here

• https://github.com/Cdiscount/speedline
• https://github.com/Cdiscount/speedline-cli

I have done the job to keep the history in the speedline-cli repository.
I haven't remove the cli.js history from the speedline repo, it can be done if you want.
I have bumped version to 2.0.0 due to the major impact.

I am not sure what to do with yarn.lock 😬

Remarks are welcome to finish this split and push the big reduction of modules needed!

from speedline.

Nice work @utix thanks!

I have an alternative proposal to consider that would avoid a major breaking change and keep the code together. We could keep speedline the same, and just add a script that publishes the same code without the bin entry and dependencies in package.json as speedline-core.

from speedline.

I can create a directory with a specific package.json to publish speedline-core using standard tools. This will avoid a script.

from speedline.

@patrickhulce I have submitted the PR to deal with a core module directly from the same repository using a specific directory with a dedicated package.json

from speedline.