Added Area-Pub, Triaged labels.

This comment was originally written by daniel.robinson...@gmail.com

The link to the github repo has changed, you can now use eith master or dev branches to achieve the exact same result, the integration-test branch has been merged down to both

Part of the point of "pub build" is that it doesn't produce any symlinks, since they're not portable. At the same time, we don't want it to copy the packages directory into every place that it could possibly be used.

For now, the best solution is to use absolute URLs to refer to the packages directory in the root of your application. Issue #15808 is tracking the addition of a transformer to fix up URLs automatically.

Added AsDesigned label.

This comment was originally written by daniel.robinson...@gmail.com

so its preferable to use:

import '../../../packages/package/name/lib.dart'

rather than:

import 'package:package/name/lib.dart';

I would have assumed that the latter should always "just work"

This comment was originally written by daniel.robinson...@gmail.com

also ../../../packages is to get from the source file location in the project to the packages directory in the project root, but that doesn't match with in my particular case which would require the build file editing to ../../packages since the built packages directory is inside build/test not the root build folder.

Currently "pub build" isn't really designed to deploy Dart entrypoints that aren't compiled to Javascript, since there aren't browser that support that in the wild. Once there are, the suggested means of deployment will be using dart2dart to compile them to a single file.

This comment was originally written by daniel.robinson.open...@gmail.com

there isn't support in the wild? one of my dart entry points is for a stand alone console app that is just run directly in the dartVM so doesnt have the lack of native browser support issue, also the other 2 entry points in my app are browser side entry points which are compiled to javascript, but the index files fail to start because it can't find the dart.js file required to boot the application on page load.

"pub build" doesn't really support deploying code to the VM yet (issue #20248). As for browser entrypoints, the .dart.js files should end up in the same location that the Dart source files were originally.

This comment was originally written by daniel.robinson.o...@gmail.com

yest the .dart.js files do end up where they originally where but when the .html file references <script src="packages/browser/dart.js"></script> it fails to find the actual "dart.js" file because it can't find the packages directory, and as I said in my previous comment making the path relative to "../../../packages/browser/dart.js" isn't particularly nice because when you build the project you then need to manually change that relative path to have one less ../ in it as the packages directory in the build folders is in a different relative location. At the end of the day it just isn't very nice and doesn't work, which is odd because I've had similar projects in the past which did work.

I remember certain builds that had multiple package directories throughout them and those package directories only contained the packages that were required in that location, so typically just browser with interop.js and dart.js in it, and everything just worked, now it doesn't sadly.

Why not just use the root-relative URL "/packages/browser/dart.js"?

Way back when we first introduced "pub build", it had specific special-case handling for the browser package that put its JS files in packages directories throughout the output. We decided that wasn't something we wanted to do for all packages, though, so we discontinued that behavior.

This issue has been moved to dart-lang/pub#1151.