devc_builder 0.1.2+1

  • README.md
  • CHANGELOG.md
  • Installing
  • Versions
  • 37

Minimal build system for dev_compiler

This is a minimal build system to help people experiment with dev_compiler.

Install

Install with pub global activate devc_builder.

Usage

Launch the build with the following command:

devc_builder main_package_path output_directory main_file_path

where

  • main_package_path is the path to the main package to build
  • output_directory guess what it is ?
  • main_file_path is the relative path of the file (without the extension) inside the main package where your main() function resides

example:

devc_builder my_app out index

will build the app inside my_app folder (that should be already "pub getted") in folder out using the file my_app/lib/index.dart as entry point.

Output

This tool will transitively examine the main package dependencies and produce a single js module for each. All the .dart file inside any package will be considered for compilation, all the other files copied to the output.

Compilation for hosted packages will be cached inside the folder .repo and reused for the next build.

Then it will create an index.html that will load all the dependencies and execute the main function in the main_file_path.

The index.html will be created with this template:

<html>
<head>
<script>
'use strict';
</script>
@IMPORT_SCRIPTS@
@BOOTSTRAP@
</head>
<body>
</body>
</html>

You can provide your own template in web/index.html:

  • @IMPORT_SCRIPTS@ will be replaced with all the import script from the dependencies and the SDK.
  • @BOOTSTRAP@ will be replaced with the bootstrap code needed to execute the main function in the main file

You can test the results using a recent chrome or translate it with babelJS.

TODO:

  • use args processing lib
  • execute babelJS / vulcanize / etc. etc.
  • try using build (can it be done ? how to handle group of sources?)

0.1.2+1

  • reset options for compiler

0.1.2

  • repo for compilation
  • copying resources
  • templating

1. Depend on it

Add this to your package's pubspec.yaml file:


dependencies:
  devc_builder: "^0.1.2+1"

2. Install it

You can install packages from the command line:

with pub:


$ pub get

Alternatively, your editor might support pub get. Check the docs for your editor to learn more.

Version Uploaded Documentation Archive
0.1.2+1 Aug 9, 2016 Go to the documentation of devc_builder 0.1.2+1 Download devc_builder 0.1.2+1 archive
0.1.2 Aug 9, 2016 Go to the documentation of devc_builder 0.1.2 Download devc_builder 0.1.2 archive
0.1.1 Aug 5, 2016 Go to the documentation of devc_builder 0.1.1 Download devc_builder 0.1.1 archive

Analysis

This feature is new.
We welcome feedback.
More details: scoring.

We analyzed this package, and provided a score, details, and suggestions below.

  • tool failures on Feb 17, 2018
  • Dart: 2.0.0-dev.20.0
  • pana: 0.10.1

Scores

Popularity:
Describes how popular the package is relative to other packages. [more]
0 / 100
Health:
Code health derived from static analysis. [more]
100 / 100
Maintenance:
Reflects how tidy and up-to-date the package is. [more]
36 / 100
Overall score:
Weighted score of the above. [more]
37

Platforms

Detected platforms: unsure

Error(s) prevent platform classification.

Suggestions

  • Fix dependencies in pubspec.yaml.

    Running pub upgrade failed with the following output:

    ERR: Could not find a file named "pubspec.yaml" in https://github.com/dart-lang/build.git 8d19de342c739397c0230d36eb5feb11f0f19726.
    
  • Fix platform conflicts.

    Make sure none of the libraries use mutually exclusive dependendencies.

  • Fix issues reported by dartanalyzer.

    dartanalyzer reported 1 error(s) and 0 warning(s).

  • The description is too short.

    Add more detail about the package, what it does and what is its target use case. Try to write at least 60 characters.

  • Package is pre-v1 release.

    While there is nothing inherently wrong with versions of 0.*.*, it usually means that the author is still experimenting with the general direction API.

  • Maintain an example.

    Create a short demo in the example/ directory to show how to use this package. Common file name patterns include: main.dart, example.dart or you could also use devc_builder.dart.