Gathering detailed insights and metrics for @lskjs/log
Gathering detailed insights and metrics for @lskjs/log
Gathering detailed insights and metrics for @lskjs/log
Gathering detailed insights and metrics for @lskjs/log
npm install @lskjs/log
58.8
Supply Chain
86.8
Quality
82.7
Maintenance
100
Vulnerability
99.1
License
v2.2.0-beta.20
Published on 03 Feb 2021
v2.2.0-beta.19
Published on 02 Feb 2021
v2.2.0-beta.17
Published on 01 Feb 2021
v2.2.0-beta.16
Published on 01 Feb 2021
v2.2.0-beta.15
Published on 01 Feb 2021
v2.2.0-beta.14
Published on 01 Feb 2021
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
38 Stars
3,457 Commits
19 Forks
10 Watching
72 Branches
14 Contributors
Updated on 30 May 2024
JavaScript (66.57%)
HTML (22.31%)
TypeScript (8.41%)
CSS (2.66%)
Shell (0.04%)
Cumulative downloads
Total Downloads
Last day
33.3%
68
Compared to previous day
Last week
11.7%
439
Compared to previous week
Last month
-27.9%
2,202
Compared to previous month
Last year
-19.5%
44,841
Compared to previous year
11
1
@lskjs/lskjs – LSK.js – command line interface scripts
1# yarn 2yarn i @lskjs/lskjs 3 4# npm 5npm i @lskjs/lskjs
Стандарт бы и 5 лет назад, но авангардисты JS создали coffescript, babel и ts, потому что JS окостенел и не двигался. Так же как и ВКшники написали свой KPHP.
В этом пути нет ничего постыдного, то что еще вчера считалось ебанистикой, завтра может захватить умы своим удобством.
У меня нет априорной аппеляции к авторитетам из ECMA.
Я делаю среду комфортную для конечного программиста, который делает продукт для клиента.
Если стандарт позволяет написать удобное решение — то придумаем как.
Если для этого придется переписать стандарт — значит перепишем.
Благо babel максимальным образом позволяет писать собственные диалекты.
Не задача должна прогибаться под решением, а решение под задачу.
repo
package
&& npm run devPackage | Description | Activity | Version | Bundle | |
---|---|---|---|---|---|
apiquery | http/s + websockets api client for Web, Node.js and React Native throw fetch or axios | ||||
apm | LSK.js – apm – module Node.js agent for Elastic APM | ||||
auth | LSK.js – auth – module for authorization by login and password and singup through social networks | ||||
autobind | LSK ux subrepo: autobind | ||||
billing | LSK.js module for adding billing in cabinet | ||||
bots | LSK.js module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-base | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-plugin | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-plugin-debug | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-plugin-menu | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-plugin-notify | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-plugin-polundra | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-plugin-portal | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-provider | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-provider-clubhouse | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-provider-discord | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-provider-instagram | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-provider-slack | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-provider-telegram | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-provider-twitter | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-provider-vk | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-provider-whatsapp | LSK.js plugin for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
bots-router | LSK.js router for @lskjs/bots module for telegram, slack, discord, whatsapp, twitter, instagram and vk bots creation | ||||
build-locales | CLI for build i18 locales from Google spreadsheet | ||||
bunyan | Light weight bunyan logger for a JSON logging library for node.js services without dtrace | ||||
config | LSK config. | ||||
db | LSK.js module for working with mongodb database | ||||
elastic | LSK.js module for elastic search | ||||
event | LSK module for event. | ||||
getspreadsheet | LSK getspreadsheet. | ||||
grant | LSK module for grant. | ||||
i18 | LSK module for internationalization with i18next. | ||||
kafka | LSK module for kafka. | ||||
launcher | LSK Launcher. | ||||
linkall | LSK link all. | ||||
log | LSK log. | ||||
log | Логгер совмещающий лучшие черты morgan, winston, bunyan, logrus. debug. Базируется на debug-level. | ||||
mailer | LSK module for send and receive emails. | ||||
mobx | LSK module for mobx. | ||||
module | Module system with dependency injection, event emitter, logger and submodules tree | ||||
permit | LSK module for one time codes and permits. | ||||
proxy | LSK module for proxy. | ||||
rabbit | LSK module for rabbit. | ||||
reactapp | LSK ux subrepo: reactapp | ||||
rlog | LSK module for remote logger. | ||||
scylla | LSK module for scylla. | ||||
sequelize | LSK module for sequelize. | ||||
server | LSK server. | ||||
server-api | LSK server-api. | ||||
sh | LSK ux subrepo: sh | ||||
sms | LSK module for sms. | ||||
tbot | LSK module. | ||||
uapp | LSK universal react app wrapper | ||||
upload | LSK module for uploading files. | ||||
utils | LSK.js – utils – helpers and functions | ||||
worker | LSK module for worker. | ||||
add-to-calendar | LSK ux subrepo: extra | ||||
article | LSK ux subrepo: article | ||||
avatar | LSK ux subrepo: avatar | ||||
button | LSK ux subrepo: button | ||||
button2 | LSK ux subrepo: button | ||||
chat | LSK ux subrepo: chat | ||||
cookie-consent | LSK ux subrepo: cookie-consent | ||||
css | LSK ux subrepo: css | ||||
dash | LSK.js – Dash – React components for your own dashboard | ||||
dashboard | LSK ux subrepo: dashboard | ||||
dev | LSK ux subrepo: ui-dev | ||||
docs | lskjs docs | ||||
downloads | LSK ux subrepo: download | ||||
extra | LSK ux subrepo: extra | ||||
flag | LSK ux subrepo: flag | ||||
form | LSK ux subrepo: form | ||||
grid | LSK ux subrepo: grid | ||||
gridtable | LSK ux subrepo: gridtable | ||||
image | LSK ux subrepo: image | ||||
landing | LSK ux subrepo: landing | ||||
link | LSK ux subrepo: link | ||||
list | LSK ux subrepo: list | ||||
modal | LSK ux subrepo: modal | ||||
navbar | LSK ux subrepo: navbar | ||||
notification | LSK ux subrepo: notification | ||||
page | LSK ux subrepo: page | ||||
progress | LSK ux subrepo: progress | ||||
scroll | LSK ux subrepo: scroll | ||||
slide | LSK ux subrepo: slide | ||||
t | LSK ux subrepo: t | ||||
tag | LSK ux subrepo: tag | ||||
theme | LSK ux subrepo: theme | ||||
typo | LSK ux subrepo: typo | ||||
ui | LSK ux subrepo: ui | ||||
ui2 | LSK ux subrepo: ui2 |
Вдохновлен:
this.useMiddlewares()
this.useRoutes()
this.useDefaultRoute()
А также:
Токен можно прикладывать следующими методами
Authorization: Bearer %USER_TOKEN%
X-Access-Token: %USER_TOKEN%
token=%USER_TOKEN%
?token=%USER_TOKEN%
LSKit принимает стоковый Bunyan логгер
1log.trace('Starting method'); 2 3if (!req.user) { 4 log.fatal('Cannot get User'); 5 throw new Error('Cannot get User') 6} 7 8log.info('Method success');
npm
v3.10 or newer (new to npm?)node-gyp
prerequisites mentioned hereBefore you start, take a moment to see how the project structure looks like:
.
├── /build/ # Директория в которую билдится проект
├── /node_modules/ # Сторонние библиотеки и утилиты
├── /src/ # Исходный код приложения
│ ├── /CoreApp/ # Базовое приложение
│ │ ├── /api/ # Интерфейс клиент-серверного взаимодействия
│ │ ├── /middlewares/ # Среднии слои express
│ │ ├── /models/ # Модели базы данных
│ │ ├── /resourses/ # Ресурсы
│ │ ├── CoreApp.js # Класс-реализация базового приложения
│ │ ├── requests.js # Реквесты приложения
│ │ └── responses.js # Респонсы приложения
│ ├── /ReactApp/ # Базовое приложение
│ │ ├── /compoents/ # React компоненты
│ │ ├── /Html/ # Класс-реализа
│ │ ├── /Html/ # Класс-реализа
│ │ ├── /Html/ # Класс-реализа
│ │ ├── /routes/ # Роутер с страницами\экранами, которые являются React компонентами
│ │ ├── /models/ # Модели базы данных
│ │ ├── /resourses/ # Ресурсы
│ │ ├── /routes/ # Роутер с страницами\экранами, которые являются React компонентами
│ │ ├── /stores/ # Сторы React приложения
│ │ ├ └── /AppStore.js # Главный стор React приложения
│ │ ├── ReactApp.client.js # Класс-реализация базового приложения на клиенте
│ │ ├── ReactApp.server.js # Класс-реализация базового приложения на сервере
│ │ ├── requests.js # Реквесты приложения
│ │ └── responses.js # Респонсы приложения
│ ├── /client.js # Точка входа Клиентского приложения
│ ├── /config # Общие настройки проекта
│ └── /server.js # Точка входа Серверного приложения
├── /test/ # Модульные и интеграционные тесты
├── /tools/ # Скрипты и утилиты для автоматизации сборки проекта
│ ├── /config.js # Конфигурация сборки проекта
│ ├── /run.js # Система запуска сборки
│ └── /webpack.config.js # Конфигурация Вебпака для клинстких и серверных бандлов
└── package.json # Список сторонних библиотек и утилит
Note: The current version of RSK does not contain a Flux implementation. It can be easily integrated with any Flux library of your choice. The most commonly used Flux libraries are Flux, Redux, and Relay.
You can start by cloning the latest version of React Starter Kit (RSK) on your local machine by running:
1$ git clone -o lego-starter-kit -b master --single-branch \ 2 https://github.com/isuvorov/lego-starter-kit.git MyApp 3$ cd MyApp
Alternatively, you can start a new project based on RSK right from WebStorm IDE, or by using Yeoman generator.
npm install
This will install both run-time project dependencies and developer tools listed in package.json file.
npm start
This command will build the app from the source files (/src
) into the output
/build
folder. As soon as the initial build completes, it will start the
Node.js server (node build/server.js
) and Browsersync
with HMR on top of it.
http://localhost:3000/ — Node.js server (
build/server.js
)
http://localhost:3000/graphql — GraphQL server and IDE
http://localhost:3001/ — BrowserSync proxy with HMR, React Hot Transform
http://localhost:3002/ — BrowserSync control panel (UI)
Now you can open your web app in a browser, on mobile devices and start
hacking. Whenever you modify any of the source files inside the /src
folder,
the module bundler (Webpack) will recompile the
app on the fly and refresh all the connected browsers.
Note that the npm start
command launches the app in development
mode,
the compiled output files are not optimized and minimized in this case.
You can use --release
command line argument to check how your app works
in release (production) mode:
1$ npm start -- --release
NOTE: double dashes are required
If you need just to build the app (without running a dev server), simply run:
1$ npm run build
or, for a production build:
1$ npm run build -- --release
or, for a production docker build:
1$ npm run build -- --release --docker
NOTE: double dashes are required
After running this command, the /build
folder will contain the compiled
version of the app. For example, you can launch Node.js server normally by
running node build/server.js
.
To check the source code for syntax errors and potential issues run:
1$ npm run lint
To launch unit tests:
1$ npm test # Run unit tests with Mocha 2$ npm run test:watch # Launch unit test runner and start watching for changes
By default, Mocha test runner is looking for test files
matching the src/**/*.test.js
pattern. Take a look at src/components/Layout/Layout.test.js
as an example.
To deploy the app, run:
1$ npm run deploy
The deployment script tools/deploy.js
is configured to push the contents of
the /build
folder to a remote server via Git. You can easily deploy your app
to Azure Web Apps,
or Heroku this way. Both will execute npm install --production
upon receiving new files from you. Note, you should only deploy the contents
of the /build
folder to a remote server.
If you need to keep your project up to date with the recent changes made to RSK, you can always fetch and merge them from this repo back into your own project by running:
1$ git checkout master 2$ git fetch lego-starter-kit 3$ git merge lego-starter-kit/master 4$ npm install
This project is licensed under the MIT License - see the LICENSE file for details
Igor Suvorov 💻 🎨 🤔 |
git checkout -b features/fooBar
)git commit -am 'feat(image): Add some fooBar'
)git push origin feature/fooBar
)No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
no binaries found in the repo
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
no SAST tool detected
Details
Reason
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
134 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More