search

TheOpenCloudEngine / uEngine5-base

uEngine5 BPMS that totally re-written in Microservices architecture. uEngine5 can act as not only a conventional Workflow or BPMS but also as a REST api orchestrator or a BPaaS (Business process as a service) of members of OCE's MSA components.
MIT License
10 stars 13 forks source link

metaworks4 에 귀속되는 vue 파일들 npm package 로 upload 하기 #37

Open jinyoung opened 6 years ago

jinyoung commented 6 years ago

향후 사용시엔 npm package.json 에서 dependency 만 걸어서 사용가능하도록 처리.

jinyoung commented 6 years ago

이것을 보고 처리 바람:

https://docs.npmjs.com/getting-started/publishing-npm-packages

jinyoung commented 6 years ago

그리고 metaworks4 ui components 들에 대한 공통 관리가 필요..

현재 uEngine5-base/front-end 에서도 , 다른 패키지들에서도 관리 중..

jinyoung commented 6 years ago

먼저 유저를 만들고:

$npm adduser

Username: (jyjang@uengine.org) jinyoungj
Password: 
Email: (this IS public) jyjang@uengine.org
Logged in as jinyoungj on https://registry.npmjs.org/.

소스폴더 가서

$ npm publish

하문 되는데,

npm ERR! This package has been marked as private
npm ERR! Remove the 'private' field from the package.json to publish it.

나면, 

$ vi package.json

해서 private:false 로 해주고,

npm ERR! you must verify your email before publishing a new package: https://www.npmjs.com/email-edit : process-codi

오류나면, 이메일 체크 해주면 된다.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/uengine/.npm/_logs/2017-12-04T11_36_08_284Z-debug.log
uengineui-MacBook-Pro:front-end uengine$ npm publish
+ process-codi@1.0.0
jinyoung commented 6 years ago

중요한거... 

 cd metworks4/src/main/resources/static
 npm publish

package.json 에 main 항목을 넣어주야 한다.. 그러면, 참조하는 곳에서 빌드 진입점으로 사용한다:

{
  "name": "metaworks4",
  "main": "src/components/index.js",          #<----------------- 이 부분
  "description": "Metaworks4 Vue JS custom HTML tags",
  "version": "1.0.0",
  "author": "jinyoung jang <jyjang@uengine.org>",
  "private": false,
  "scripts": {
    "dev": "cross-env NODE_ENV=development webpack-dev-server --open --hot",
    "build": "cross-env NODE_ENV=production webpack --progress --hide-modules"
  },
  "dependencies": {
    "vue": "^2.3.3"
  },
  "devDependencies": {
    "babel-core": "^6.0.0",
    "babel-loader": "^6.0.0",
    "babel-preset-env": "^1.5.1",
    "cross-env": "^3.0.0",
    "css-loader": "^0.25.0",
    "file-loader": "^0.9.0",
    "vue-loader": "^12.1.0",
    "vue-template-compiler": "^2.3.3",
    "webpack": "^2.6.1",
    "webpack-dev-server": "^2.4.5"
  }
}
jinyoung commented 6 years ago