GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com โ€” ionic/core/scripts at master ยท ModusCreateOrg/ionic

Expand file tree

/

scripts

/
Copy path

Directory actions

More options

More options

Directory actions

More options

More options

Latest commit

 

History

History
History
 
 
/

scripts

/
Copy path

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
screenshot
screenshot
 
 
testing
testing
 
 
api-spec-generator.js
api-spec-generator.js
 
 
cdn-loader.js
cdn-loader.js
 
 
clean.js
clean.js
 
 
copy-cdn-loader.js
copy-cdn-loader.js
 
 
readme.md
readme.md
 
 
swiper.rollup.config.js
swiper.rollup.config.js
 
 
treeshaking.js
treeshaking.js
 
 
update-readme.js
update-readme.js
 
 

readme.md

Outline

Build

1. Clone ionic

[email protected]:ionic-team/ionic.git
cd ionic

2. Run npm install

cd core npm install

Notice that @ionic/core lives in core.

3. Run npm start

Make sure you are inside the core directory.

npm start

With the dev command, Ionic components will be built with Stencil, changes to source files are watched, a local http server will startup, and http://localhost:3333/ will open in a browser.

4. Preview

Navigate to http://localhost:3333/src/components/. Each component has small e2e apps found in the test directory, for example: http://localhost:3333/src/components/button/test/basic

As changes are made in an editor to source files, the e2e app will live-reload.

How to contribute

  1. npm start allows you to modify the components and have live reloading, just like another ionic app.

  2. When everything looks good, run npm run validate to verify the tests linter and production build passes.

Deploy

  1. npm run prepare.deploy
  2. Review/update changelog
  3. Commit updates using the package name and version number as the commit message.
  4. npm run deploy
  5. ๐ŸŽ‰
You are visitor 01402503 โ€” GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800ร—600. No cookies required.