New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Make it possible to build out projects using native modules #1049

Open
matthewp opened this Issue Jul 23, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@matthewp
Member

matthewp commented Jul 23, 2018

With native modules in browsers, some teams might choose to use those in development. It could look something like this:

development.html

<title>Our app</title>
<script type="module" src="./app.js"></script>

app.js

import { Component } from "//unpkg.com/can@5/core.mjs";

Component.extend({ ... })

Currently, trying to build this in steal-tools will cause errors.

To make this work we would want:

  • Support for loading modules that start with either /, //, http and https which we currently can't do.
  • Since unpkg supporters semver, it would be great if we could do semver to normalize to the same module. For example //unpkg.com/can@5/core.mjs and //unpkg.com/can@^5.0.0/core.mjs should normalize to the same module.

@matthewp matthewp changed the title from Proposal: Make it possible to build out projects of native modules to Proposal: Make it possible to build out projects using native modules Jul 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment