Skip to content
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

Test this route4me-node as 3d-party dependency for webpack #50

Open
maxkoryukov opened this issue Feb 28, 2017 · 0 comments
Open

Test this route4me-node as 3d-party dependency for webpack #50

maxkoryukov opened this issue Feb 28, 2017 · 0 comments
Assignees
Labels

Comments

@maxkoryukov
Copy link
Contributor

ancestor of #16

WebPack uses the concept of targets and provides module resolution rules (https://webpack.js.org/concepts/module-resolution/)

Module resolution depends on target, but always checks fields in package.json :

  • target web : fields browser, module, main
  • target node: fields module, main

So, when the package is used as

  • pure Node package - main will be used
  • by WebPack - browser or module will be used (depending on target)
  • by browser - browser version will be used

BTW: for published on NPM version we will get the public CDN: https://unpkg.com/

What to do in this issue:

Create a project, and use route4me-node as a dependency.
Then pack this project with webpack, and look at the result. The result MUST LOOKS BRILLIANT!!! Ho ho ho

@maxkoryukov maxkoryukov added this to the 1.0.0 improvements milestone Feb 28, 2017
@maxkoryukov maxkoryukov self-assigned this Feb 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant