yurickh / ouxe Goto Github PK

Right now we leave the exercise to the user to figure out exactly what happened. We can be better than that :)~

Something that I've been doing in my repos is to rename the default branch into main.
It would be great if ouxe had support to, when running npx ouxe default-branch main, execute in order:

• create and push the main branch
• update all PRs in GitHub to point to the new branch
• change it to default in GitHub
• change all occurrences of the old default branch name in the CI/CD setup
• remove the old default branch on both local and remote

We want to run tests and create builds when Pull Requests are created, in order to verify their mergeability

Preferably the Contributor Covenant

Running ouxe in the root of a monorepo with yarn workspaces will warn with:

error Running this command will add the dependency to the workspace root rather than the workspace itself, which might not be what you want - if you really meant it, make it explicit by running this command again with the -W flag (or --ignore-workspace-root-check).

We probably want to add the --ignore-workspace-root-check flag for installs that should go on the root, like eslint or prettier.

When executing npx ouxe, it prints out

/Users/yurick/github/oss/ouxe/node_modules/.bin/ouxe: line 1: syntax error near unexpected token `('

And then the whole of the build file (namely lib/ouxe.js, which is the one that goes to .bin`).

I couldn't find a syntax error in the built package, so I suspect this is related to the node version npx is using to execute.

Although it's a really good library, micro bundle is intended to be used to bundle small packages for the browser, thus it acts and produces a build that it's not really aligned with the goal of this package: to be used in a node environment.

List of possible alternatives:

• tsdx
• pure rollup

(feel free to recommend alternatives in the comments)

This is needed in order to support proper .eslintrc creation, as we need to conditionally add libraries like @typescript-eslint for typescript, or prettier-config-eslint if prettier is detected.

We should be able to detect:

• typescript
  • @typescript-eslint/eslint-plugin
  • @typescript-eslint/parser
• prettier
  • eslint-config-prettier
• react
  • eslint-config-react-app and its peers
  • eslint-plugin-react-hooks
• babel
  • babel-eslint

Frequently the process just hangs while installing (which could be solved by checking out pnp) or timeouts during the prettier integration test.

• .gitignore