Skip to content

feat: support packageManager via nativescript.config #5595

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

Closed
NathanWalker opened this issue Oct 19, 2021 · 1 comment
Closed

feat: support packageManager via nativescript.config #5595

NathanWalker opened this issue Oct 19, 2021 · 1 comment
Assignees

Comments

@NathanWalker
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Currently when switching between yarn workspace enabled projects to npm bound workspaces we need to switch the cli package-manager properly.

Describe the solution you'd like

Instead the cli should look for:

import { NativeScriptConfig } from '@nativescript/core';

export default {
	id: 'org.nativescript.app',
	android: {
		v8Flags: '--expose_gc',
		markingMode: 'none',
	},
	appPath: 'src',
        // New CLI properties
	cli: {
		packageManager: 'yarn',
	}
} as NativeScriptConfig;

To determine it's package-manager settings when running/building projects.

Describe alternatives you've considered

Possibly using .nsrc however the nativescript.config is perfect place to manage this option.

Additional context

Pains when switching between yarn enabled project workspaces to plugin workspaces you have to be sure cli package-manager is set right.

@NathanWalker
Copy link
Contributor Author

implemented on next now 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants