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

Bump ncc to 0.30 #325

Closed
wants to merge 1 commit into from
Closed

Bump ncc to 0.30 #325

wants to merge 1 commit into from

Conversation

t-botz
Copy link

@t-botz t-botz commented Aug 30, 2021

@zeit/ncc is not maintained and renamed to @vercel/ncc
References:

Sidenote: Looks like its been a while since the dist folder has been updated, time for a release?

@@ -2,6 +2,7 @@
"compilerOptions": {
"target": "es6", /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019' or 'ESNEXT'. */
"module": "commonjs", /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', or 'ESNext'. */
"moduleResolution": "node",
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ncc version 0.28.0 requires that for some reason.
I am a bit surprised that it is not the default. Quoting typescript doco :

There are two possible module resolution strategies: Node and Classic. You can use the --moduleResolution flag to specify the module resolution strategy. If not specified, the default is Node for --module commonjs, and Classic otherwise (including when --module is set to amd, system, umd, es2015, esnext, etc.).

@SVilgelm
Copy link
Member

close in favor of #404

@SVilgelm SVilgelm closed this Feb 24, 2022
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

Successfully merging this pull request may close these issues.

None yet

2 participants