• Help screen
• Hook progress screen
• Result screen

Description

https://github.com/siddharthkp/auto-install#readme

Suggestions

• Use it at watch hook
• Possibly fork it so can use in config:watch also for clipped.config.js?

For example

const config = createChainable({
  abc: [
    {text: 'abc'}
  ]
})

If i do something like

config.abc.text

Since the array abc does not have text property, it should try accessing conffig.abc[0].text

This is useful tools that can have multiple sets of config e.g. rollup

• Make a clip like a preset that exports the a async function returning config
• Make a clip for making clips
• Download from clip repo if detected that it is not in cache

Description

Some tools like babel and typescript have additional functions in their cli, so its actually better to like create a config file rather than trying to recreate their cli behaviours using their api like @babel/core

Suggestions

• Create a directory called .clipped for storing those config files
• Do it like @vue/cli's ConfigTransform?

Proposal for 2.0 🤔

Objectives

0. Use unclip as new name

1. Use 'plugin' concept instead of existing 'preset'

Problem

Currently a preset cannot really be reused because they have app specific constants such as entry path, app name.

Solution

App specific options can be passed in .env file, plugins get options from function call

// plugin-blabla.js
module.exports = (opt) => ({config, on, env, tools}) => ({
  return {
    docker: {
      "HttpHeaders": {
        "MyHeader": opt.header
      }
    }
  }
})

// clipped.config.js
module.exports = () => [
  require('@clipped/plugin-blabla')({header: 'someheader'})
]

2. Make config changes more convenient.

Problem

Current way needs a really long object chain before even reaching the config.

Current way:

module.exports = clipped => {
  clipped.config.webpack.plugins.push(/* blablabla */)
}

Solution

Correspond export's object keys to correspond to config, and mutation will be similar to immer's behaviour

New way:

// base.js
module.exports = () => () => ({
  webpack: {
    entry: [],
    rules: {}
  }
})

// clipped.config.js
module.exports = () => () => {
  return {
    webpack: config => plugins.push(/* blablabla */)
  }
}

3. Make result config more verbose

Problem:

Currently when user edit a preset he actually does not know how the final config object is like.

Solution:

Maybe stream to console / json file?

4. Better way to express config relations

Problem

For instance the way rollup use babel config and that of webpack is 99% similar but not same

Solution

https://github.com/clippedjs/jointed/issues/24

5. Revamp event emitter and generator

Problem

Current init does not work anymore because didn't scan nested folder structure on github

Solution

Make create a reserved command, which lets user choose plugins to install first, and then use init command which is currently used for running yeoman generator, make it empty instead initially

6. Replace flow with typescript

Progress

• Use unclip as new name
• Rewrite presets as plugins
• describe function to describe preset (to be done in next release)
• transform function to copy config from e.g. .babelrc (to be done in next release)
• Support (opt) => [(clipped) => {}] besides (clipped) => {} for clipped and the plugins
• Support using return value of plugin to modify config
• Report resulting config to user
• Use aliasing for config relationships
• Add reservedcreate hook in cli
• Replace flow with typescript
• Add XO linting
• Use AVA instead of mocha for testing

Currently StandardJs reports error on custom flowtype, might be due to wrong setup.

What was your expectation?

What is the actual behaviour?

Suggested changes

• [ ]

https://docusaurus.io/

Description

Right now a problem is that config often depends on the hook triggered and options passed, but right now api.config is immediately mutated

Suggestions

• Use chain as a function so the mutation function can be queued, and executed on hook call instead of immediately

Description

Suggestions

Description

Currently CLI is getting a bit bloaty due to added hooks, and is not clearly separated in terms of initializing clipped.

Think might be better to move it to separate package @clipped/cli like @babel/cli

Maybe do it before cac migration

And I think it will be awesome if when some cases can be automated for users.

Examples:

• When user installed React and then runs clipped dev, cli can assume behaviour like create-react-app. So install webpack, babel and react plugin and then run the dev hook
• If detect index.html in src, automatically use it as template in html-webpack-plugin

Possible issues:

• How do I know if user want to use Webpack or Rollup?
• How to cleanly revert if, e.g. user uninstalls React and install Vue

Suggestions

Be able to keep running clipped.config.js and return clipped.config

Support .forEach(), .map() in primitives

Description

https://github.com/GoogleChromeLabs/carlo

Suggestions

The devDependency codacy-coverage was updated from 3.0.0 to 3.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

codacy-coverage is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Plugins

• Babel
• Rollup
• Webpack
• Docker
• Typescript
• Lint
  • Eslint
• Test
  • Jest

Since some cli do not have JS API, might offer method to convert JSON to arguments string

Version 3.3.1 of lerna was just published.

This version is covered by your current version range and after updating it in your project the build failed.

lerna is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Description

module.exports = () => [
  api => api.describe({
    id: 'org.clipped.webpack',
    name: 'Webpack plugin'
    description: 'Webpack bundler support',
    after: ['org.clipped.babel'],
    before: ['org.clipped.typescript']
  })
]

Suggestions

What was your expectation?

Codecov to analyse the report on website

What is the actual behaviour?

The report was successfully uploaded, but on the website Codecov said error

Suggested changes

No clue yet

https://github.com/semantic-release/semantic-release

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Description

Currently need to install clipped globally and then clipped create

Suggestions

• Make a create-clipped package that runs clipped create
• Make it so clipped create <folder-name> creates folder and go into it
• In package.json add npm scripts according to hooks

Test cases:

• Hooks
• Presets

Description

https://github.com/TheOnlyArtz/artzlogger

Suggestions

A clip exposes a cli.js and a index.js respectively. We trigger actions with the cli from actions, but when we attempt an override, index.js will export is config and functions

Description

Currently it is hard to support a standard config cross build tools

Suggestions

Need a way to reflect e.g. clipped.config.name to clipped.config.webpack.plugins .html.args[0].title which is clumsy and hard to remember

Description

https://github.com/cacjs/cac

Suggestions

Description

Installs, but when tying t use create or init, it errors.

λ clipped create
module.js:550
    throw err;
    ^

Error: Cannot find module '../dist/src'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (C:\Users\Mark\AppData\Roaming\npm\node_modules\clipped\bin\clipped:3:1)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)

Using node 8.12 and npm 6.4.1

Suggestions

Description

Suggestions

Description

After trials it actually seems like having separate plugins instead of templates is better, but then how to guide users who are used to create-react-app or @vue/cli to use it is a problem, because it is possible they don't even know what is the difference between Webpack and Rollup, and why need to setup Babel separately.

Suggestions

• Make create hook more like a survey like 'Do you want to build a library or website' -> 'Do you want to use react / vue / angular' -> 'Do you want to use typescript' ?

• Or make recipes on documentation like parceljs's

https://www.npmjs.com/package/execa

What was your expectation?

The project to be re-transpiled and active page hot-reloaded

What is the actual behaviour?

It was re-transpiled but needs to reload the page to take effect

Suggested changes

• Might be problem with dev-server options

Should install dependencies before using

C:\source
λ npm i -g [email protected]
C:\Users\Mark\AppData\Roaming\npm\clipped -> C:\Users\Mark\AppData\Roaming\npm\node_modules\clipped\bin\clipped
+ [email protected]
updated 1 package in 15.395s

then:

C:\source
λ cd clipTest\

C:\source\clipTest
λ clipped init

Usage:    clipped ACTION

Actions:
version, create, config:watch


C:\source\clipTest
λ clipped create
{ Error: spawn npm ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
    at onErrorNT (internal/child_process.js:362:16)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn npm',
  path: 'npm',
  spawnargs: [ 'init' ] }

C:\source\clipTest
λ ls

C:\source\clipTest
λ clipped

Usage:    clipped ACTION

Actions:
version, create, config:watch


C:\source\clipTest
λ clipped create
{ Error: spawn npm ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
    at onErrorNT (internal/child_process.js:362:16)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn npm',
  path: 'npm',
  spawnargs: [ 'init' ] }

C:\source\clipTest
λ clipped version
2.1.4

Originally posted by @devtech8 in #118 (comment)

Make the scripts run from the clips rather than target directory, then pass the target directory path into it as src and dist path

Checklist:

• Make actions use npm scripts rather than calling node_modules bin
• Make webpack for frontend work with change in src and dist path
• Use backpack for backend, referring to frontend
• Abstract getting clips into a utility function for possible future extensions (e.g. github, npm package)

Maybe with VuePress or GitBook?

https://www.npmjs.com/package/yarn-install
https://github.com/jonschlinkert/yarn-api

Description

Suggestions

Presets, generators, clipped itself

Clone clip from corresponding repo
http://www.nodegit.org/guides/cloning/

The devDependency lerna was updated from 3.3.2 to 3.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lerna is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

npx --package yo --package @sonicdoe/generator-node