Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • T TIDO
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 108
    • Issues 108
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
    • Jira issues
    • Open Jira
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • subugoe
  • emo
  • TIDO
  • Issues
  • #105

Closed
Open
Created Nov 04, 2020 by schneider210@schneider210Contributor13 of 14 tasks completed13/14 tasks

EMo release via npm

A project needs a convenient way to integrate the Viewer

Goals:

    1. publish the Viewer as npm package
    1. install the Viewer as npm package
    1. integrate the Viewer

Publish

  • what to publish (build && statics && usual suspects): setup package.json
  • setup package scope (GitLab)
  • create access token (GitLab)
  • configure registry setup / .npmrc
  • configure publishing setup in package.json

Install

  • setup registry according to package scope
  • install the npm package

Integrate

  • import js modules (main.js)
  • import css (main.scss)
  • copy config-object (project's entrypoint)

TODOs:

  • (automate) renaming of build files from checksums to readable names to ease the integration
  • patch / change build pipeline to end up with a single js / css file instead of 3 (if applicable)
  • release the Viewer as standalone package
  • accordance on licensing
Edited Nov 30, 2020 by schneider210
Assignee
Assign to
Time tracking