createDeprecatedModule should be striped from production builds.

[krisselden]

No description provided.

[rwjblue]

Why? Having the deprecated shims present in dev builds with a deprecation, but not present in prod builds would obviously be a breaking change.

[rwjblue]

I could see doing a major bump here to drop them completely though.

[krisselden]

This was still in our production build

ember-resolver/vendor/ember-resolver/legacy-shims.js

Lines 5 to 9 in 5c6b080

	Ember['default'].deprecate(
	'Usage of `' + moduleId + '` module is deprecated, please update to `ember-resolver`.',
	false,
	{ id: 'ember-resolver.legacy-shims', until: '3.0.0' }
	);

[rwjblue]

Right, that is because there is no infrastructure for auto-stripping these things in general. ember-cli/rfcs#50 attempts to address this. The Ember.deprecate call there will be a noop in production builds of Ember though.

[stefanpenner]

@chadhietala this may be good task for you svelte tooling