CI / dev experience remaining issues · uber/manifold#28

2019-09-12T18:52:27.000Z

- [ ] add readme to npm homepage https://www.npmjs.com/package/@mlvis/manifold - [ ] add publishing script to Travis CI - [ ] auto bump version in the main package.json (currently `ocular-publish` only bumps versions in `modules` package.json - [ ] install storybook for development purpose - [x] properly structure published module (below is the current structure, which causes `import Manifold from '@mlvis/manifold'` to not work #27 ![image](https://user-images.githubusercontent.com/4994677/64812234-a93f2380-d553-11e9-9579-c921c9e7d148.png) - [ ] add depcheck - [ ] use gh-pages module to deploy website

(5 comments) (0 reactions) (0 assignees)JavaScript (1,619 stars) (119 forks)batch import

dev exphelp wanted

説明

add readme to npm homepage https://www.npmjs.com/package/@mlvis/manifold
add publishing script to Travis CI
auto bump version in the main package.json (currently ocular-publish only bumps versions in modules package.json
install storybook for development purpose
properly structure published module (below is the current structure, which causes import Manifold from '@mlvis/manifold' to not work #27
add depcheck
use gh-pages module to deploy website

コントリビューターガイド

技術スタック: javascriptnodejs
領域: devopsci cddeveloper experience
Issue 種別: devops
難度: 3
推定時間: 1-2 days
活動状況: stale
明確さ: mostly clear
前提条件: Node.js package managementTravis CInpm publishingstorybook basics
初心者向け度: 30
調査方針: Review the remaining checklist items and the linked issue #27 for the package structure problem. Examine the repository's current CI configuration (likely Travis CI) and package.json files, specifically noting the ocular publish tool. Check the 5 comments for any additional context or decisions. Then, for each uncompleted task, propose a plan to implement it, starting with the most straightforward ones like adding a README to the npm page.