1aron / techor Goto Github PK

View Code? Open in Web Editor NEW

8.0 2.0 1.0 2.54 MB

A monorepo framework integrating first-class packages and build systems

License: MIT License

Shell 0.06% TypeScript 91.78% JavaScript 7.04% Handlebars 1.12%

authoring config log technology

techor's Introduction

techor

A monorepo ecosystem integrating first-class packages and build systems

Ecosystem

Build System

techor - A monorepo build system and workflow

Convention

techor-conventional-commits - A human-readable set of conventional commits, with version rules and changelog groupings
conventional-changelog-techor - Beautiful changelog based on Techor's conventional commits

Release

semantic-release-config-techor - Techor's semantic release config for publishing workspace packages

Packing

pack - Bundling your TypeScript and CSS packages with zero configuration

Versioning

version - Smartly bump all workspace-dependent packages to specific versions

Linting

eslint-config-techor - Techor's eslint config
commitlint-config-techor - Check your commits with Techor's commitlint config

Testing

jest - Techor's jest preset to improve performance
jest-dom - Techor's jest preset for DOM

Continuous Integration

techor-github-actions - A set of GitHub Actions for techor ecosystem includes PR title checks

Utilities

extend — Deeply extend objects ~380B
a plain obj — Is it a plain object? ~100B
cross import — Import .ts, .mjs, .cjs files across environments as JavaScript modules
explore config — Explore multi-format JavaScript module configuration
fs — A human-friendly file system with glob patterns
glob — A human-friendly set of glob utilities
npm — Get, query, and read such as package workspaces via NPM/PNPM.

Built on the top

turborepo - A high-performance build system for monorepo
esbuild - An extremely fast JavaScript and CSS bundler and minifier
semantic-release - Fully automated version management and package publishing
typescript - A strongly typed programming language that builds on JavaScript
commitlint - Lint commit messages
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata
eslint - Find and fix problems in your JavaScript code
husky - Modern native Git hooks made easy
jest - Delightful JavaScript Testing.

Who's using techor?

Master CSS - A Virtual CSS language with enhanced syntax

Contributing

Please see the documentation CONTRIBUTING for workflow.

techor's People

Contributors

Stargazers

Watchers

Forkers

0miles

techor's Issues

The automated release is failing 🚨

🚨 The automated release from the `main` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Missing `package.json` file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Missing `package.json` file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the `main` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

✨ Support `import.meta.url` in CJS

Description

evanw/esbuild#1492

__dirname -> path.dirname(fileURLToPath(import.meta.url))

The automated release is failing 🚨

🚨 The automated release from the `main` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.

Good luck with your project ✨

Your semantic-release bot 📦🚀

🐞 URLs and Users within `` '' "" must be excluded.

Description

https://github.com/1aron/techor/blob/d639c758c92a2366f304e23bc584a9c4e61abeee/packages/conventional-changelog-config/src/writer-opts.ts#L47-L64

Reproduction

Parsing the following subjects must be avoided.

Fix: `@1aron` '@1aron' "@1aron"

Fix: `#1` '#1' "#1"

System Informations

macOS

🐞 `@techor/pack` packaging result is different from `esbuild`

Description

esbuild src/index.ts --bundle --minify --outfile=dist/index.js --format=cjs --platform=node

different from

techor pack --bundle --platform node

We should test its consistency.

Reproduction

No response

System Informations

macOS

🐞 "use client" and "use server" directives are removed

Description

rollup/rollup#4699

💖 Replace chalk with picocolors

Description

$ node ./benchmarks/size.js
Data from packagephobia.com
  chalk       101 kB
  cli-color  1249 kB
  ansi-colors  25 kB
  kleur        21 kB
  colorette    17 kB
  nanocolors   16 kB
+ picocolors    7 kB

Library loading time:

$ node ./benchmarks/loading.js
  chalk          6.167 ms
  cli-color     31.431 ms
  ansi-colors    1.585 ms
  kleur          2.008 ms
  kleur/colors   0.773 ms
  colorette      2.476 ms
  nanocolors     0.833 ms
+ picocolors     0.466 ms

Benchmark for simple use case:

$ node ./benchmarks/simple.js
  chalk         24,066,342 ops/sec
  cli-color        938,700 ops/sec
  ansi-colors    4,532,542 ops/sec
  kleur         20,343,122 ops/sec
  kleur/colors  35,415,770 ops/sec
  colorette     34,244,834 ops/sec
  nanocolors    33,443,265 ops/sec
+ picocolors    33,271,645 ops/sec

Benchmark for complex use cases:

$ node ./benchmarks/complex.js
  chalk            969,915 ops/sec
  cli-color        131,639 ops/sec
  ansi-colors      342,250 ops/sec
  kleur            611,880 ops/sec
  kleur/colors   1,129,526 ops/sec
  colorette      1,747,277 ops/sec
  nanocolors     1,251,312 ops/sec
+ picocolors     2,024,086 ops/sec

The automated release is failing 🚨

🚨 The automated release from the `main` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.