text:
make iso prop available on $i18n object

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

I need to send the iso code to my CMS to retrieve content in the correct language
Describe the solution you'd like

make the iso code available directly on the $i18n object in the same way the locale code is
Describe alternatives you've considered

As all the locales are available on the $i18n object as an array this can be filtered with the locale code to retrieve the corresponding iso code
Additional context

Since locale objects accept any property, I wouldn't want to special-case the iso code as then someone could ask for some other to be exposed and in the end, it would only make sense to expose everything.
You can easily create a global mixin or inject the iso code through a separate plugin so I would consider that to be a viable and easy to implement alternative. Or just have a computed property if you need it only in one file.

Alternatively, I could expose a property like $i18n.localeProperties which would be a direct mapping to the object for current locale.

Alternatively, I could expose a property like $i18n.localeProperties which would be a direct mapping to the object for current locale.

This would be perfect and I think make more sense that just exposing iso for the reasons you suggest 👍

$i18n.localeProperties property added in https://github.com/nuxt-community/i18n-module/releases/tag/v6.18.0

$i18n.localeProperties property added in https://github.com/nuxt-community/i18n-module/releases/tag/v6.18.0

authors: rchl timdiacon


text:
@nuxtjs/sitemap version 3 missing

Hi,
I'm using @nuxtjs/sitemap@^3.4.1 on my nuxt 2 project
On a clean install I'm getting
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @nuxtjs/sitemap@^3.4.1.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

which doesn't make sense until i check the npm page and discover that none of the v3 version are listed
https://www.npmjs.com/package/@nuxtjs/sitemap?activeTab=versions
How can I fix this issue?
Thanks

You need to pin the version to 2.x if you're using Nuxt 2.
Not sure where you got this version from?

your're right, i've updated it in december and didn't have any issue until now 🤔
Thanks for your help!

source: gharchive/issue

repo: nuxt-modules/sitemap

license: MIT

license_type: permissive

license_source: github-api


text:
InjectPosition : 'last' not working with vuetify

Version Information

@nuxtjs/tailwindcss: Latest Version
Nuxt: Version 3.8.2

Reproduction Scenario
In my project, Vuetify is incorporated, and I use vite-plugin-vuetify for treeshaking purposes.
I've turned off Vuetify's CSS helpers and implemented Tailwind CSS.
Tailwind CSS functions perfectly except when used within a Vuetify component.
For instance, a Vuetify component like VCard is styled with padding:0,
So when we try to apply a Tailwind class such as p-10 it will fail, as it gets overridden by padding:0.
Given that vite-plugin-vuetify creates separate CSS files for each Vuetify component, like ,
Specifying 'injectPosition' as 'last' doesn't solve this issue.
Upon inspecting the DOM, I can verify that the Tailwind class is indeed applied but is negated by the existing padding:0.
Manually removing padding:0 enables the Tailwind p-10 class to function as intended.
Any help is deeply appreciated.

Is it possible for you to pass styles: false to the Vite plugin while adding vuetify/styles to nuxt.options.css?

Hello @ineshbose, that wouldn't work. The styles option for the vite plugin was responsible for each component style, while the vuetify/styles was responsible for other things like $utilities, $reset, etc..
We actually need both. However what i end up doing was, use the important option in tailwindcss config.
Thank you so much for looking in to this

Did you find a solution to this @stephenjason89? Might be helpful later for someone else in the same boat!

repo: nuxt-modules/tailwindcss


text:
Duplicate  and

Discussed in https://github.com/nuxt/nuxt.js/discussions/10612

Originally posted by Envoy49 August  1, 2022
Hi, I have got two types of browser warnings asking me to add "crossorigin" and "as" to the relevant preloaded JS resources created by NUXT itself.
I have done all research I could, tried different webpack configurations and failed all the time.
I don't understand what is the problem and what is the source of it? Is it because of nuxt-bridge I am using?
Seen similar problems but people had access to the html tag to be able to add missing property, in my case I don't understand how I can manipulate it.
Using : "nuxt-edge": "^2.16.0-27358576.777a4b7f"    and    "@nuxt/bridge": "npm:@nuxt/bridge-edge", node version: 14.8

I think that I should be able to fix it in nuxt.config but not sure what needs to be done. Will appreciate any help
UPDATE:
I am getting script tags with "as" in the page source. Wondering why the warning still appearing in the console

    <link rel="preload" href="/_nuxt/app~._.nuxt_A.js" as="script" />
    <link rel="preload" href="/_nuxt/app~._.nuxt_A.css" as="style" />
    <link rel="preload" href="/_nuxt/app~._a.css" as="style" />
    <link rel="preload" href="/_nuxt/app~._a.js" as="script" />
    <link rel="preload" href="/_nuxt/app~._l.js" as="script" />
    <link rel="preload" href="/_nuxt/app~._layouts_d.js" as="script" />
    <link rel="preload" href="/_nuxt/app~._n.js" as="script" />
    <link
      rel="preload"
      href="/_nuxt/app~._node_modules_atlas_node_modules_vue_dist_vue.runtime.esm.js~8cb01656.js"
      as="script"
    />
    <link
      rel="preload"
      href="/_nuxt/app~._node_modules_atlas_src_c.js"
      as="script"
    />
    <link rel="preload" href="/_nuxt/app~._node_modules_ba.js" as="script" />
    <link rel="preload" href="/_nuxt/app~._node_modules_c.js" as="script" />
    <link rel="preload" href="/_nuxt/app~._node_modules_h.js" as="script" />
    <link rel="preload" href="/_nuxt/app~._node_modules_i.js" as="script" />
    <link rel="preload" href="/_nuxt/app~._node_modules_vue-c.js" as="script" />
    <link
      rel="preload"
      href="/_nuxt/app~._node_modules_vue_dist_vue.runtime.esm.js~6acccc03.js"
      as="script"
    />
    <link
      rel="preload"
      href="/_nuxt/header-bar-mobile-menu~._node_modules_atlas_src_components_HeaderBar_HeaderBarMobileMenu.vue~0.js"
      as="script"
    />
    <link rel="preload" href="/_nuxt/pages/index~._c.css" as="style" />
    <link rel="preload" href="/_nuxt/pages/index~._c.js" as="script" />
    <link
      rel="preload"
      href="/_nuxt/pages/_~pages/index~pages/preview/_~pages/search~._c.js"
      as="script"
    />
    <link rel="preload" href="/_nuxt/0.js" as="script" />

I can see this PR ----> https://github.com/nuxt/nuxt.js/pull/7709 merged back in 2020, related to missing "crossorigin"
Wondering if it fixed issue and I am not using the version which has it missing.
UPDATE:
I just discovered that the same scripts are at the bottom of my page and has "crossorigin" attribute.
So basically first error is coming from the HEAD html tag where I got all my preloaded scripts without "crossorigin" tag and the second error message is coming from bottom of the page where I have "crossorigin" tag withouth "as".

    <script src="/_nuxt/app~._.nuxt_A.js" defer crossorigin></script>
    <script src="/_nuxt/app~._a.js" defer crossorigin></script>
    <script src="/_nuxt/app~._la.js" defer crossorigin></script>
    <script src="/_nuxt/app~._m.js" defer crossorigin></script>
    <script src="/_nuxt/app~._n.js" defer crossorigin></script>
    <script src="/_nuxt/app~._node_modules_an.js" defer crossorigin></script>
    <script
      src="/_nuxt/app~._node_modules_atlas_src_c.js"
      defer
      crossorigin
    ></script>
    <script src="/_nuxt/app~._node_modules_ba.js" defer crossorigin></script>
    <script src="/_nuxt/app~._node_modules_c.js" defer crossorigin></script>
    <script src="/_nuxt/app~._node_modules_h.js" defer crossorigin></script>
    <script src="/_nuxt/app~._node_modules_i.js" defer crossorigin></script>
    <script src="/_nuxt/app~._node_modules_vue-c.js" defer crossorigin></script>
    <script
      src="/_nuxt/app~._node_modules_vue_dist_vue.runtime.esm.js~6acccc03.js"
      defer
      crossorigin
    ></script>

This will be fixed when we upgrade to the new version of vue-bundle-renderer.

@danielroe Do you know how long it will take?

Should be this week.

@danielroe I hope all will be fine and soon :)

@duboloms please bit a bit patient. 😺 🤗

@duboloms please bit a bit patient. 😺 🤗

@danielroe I hope all will be fine and soon :)

vue-bundle-renderer will be updated with #461. But this pr has got some error on testing process. They will be merge pr after the errors are fixed.

@danielroe, I was wondering if this is available for upgrade yet or it hasn't been released yet? Which version I should update it to?

Same. I installed latest version but vue-bundle-renderer still 0.3.9

Yes, the automatic release didn't trigger for some reason.

@danielroe, could you please let us know when the release will be available?

@danielroe Sorry, do we have any news on this one being released?

Apologies @Envoy49 🙏 This should be released in the latest edge version.

Thanks for your hard work @danielroe , can confirm that it has been fixed.

I'm using nuxt3, where I had the same problem, I changed the ssr to true, I know the problem comes from the preload but I really don't know why this fixed the problem.

authors: DulcePC Envoy49 antlionguard danielroe duboloms kissu

repo: nuxt/bridge


text:
NODE_ENV either set to development or production, no way to add staging environment

Hello,
I am trying to have three separate environments using nuxt, but NODE_ENV is always development unless I use nuxt start which switches it to production.
How would I go about creating a staging environment? I tried NODE_ENV=staging nuxt in my package.json but it has been unsuccessful so far.
Thanks.

What is setting in nuxt.config.js:
env:{
  NODE_ENV: 'staging'
}

I found an alternative. I am using dotenv to load environment variables, I just created a variable in nuxt.config.js to make use of the NODE_ENV:
env: {
    environment: process.env.NODE_ENV
}

Should support that out of the box though.


text:
Problems with dev dependencies when deploying to Azure Web App

I'm just trialing out nuxt.js and i'm trying out deployment to an Azure Web App.
I'm experiencing issues when running npm run build requiring the dev dependencies (es-lint, etc) when building.
This happens even though the NODE_ENV environment variable is set to production and even if I run the command with  a NODE_ENV prefix
set NODE_ENV=production&& npm run build
I can get it to build if I install the dev dependencies first.
I'm using node@6.9.5 and npm@3.10.10

Update: It seems like this was caused my ESLint being set to run on save in nuxt.config.js (set by the starter kit).


text:
Add data and/or content folder for static generated part of application

I plan on using nuxt generate to create static sites and blogs. Other alternates, obviously, are Jekyll, Hexo, Hugo, etc.
Currently, like the mentioned alternatives, nuxt provides:

layouts or templates
components or partials
dynamic urls or routing
assets (css, images, etc.)

However, the main features it does not provide:

Data files for reusable information that can be used inside pre-compiled files (this can be done inside HTML templates locally with the data component property, but there is no global data configurations that can be used inside markdown files before they are compiled as vue components)

Front-matter/metadata that facilitates content organization (e.g. by date, title, category etc.)

Before I go off and try to incorporate these features on my own, my question is: would it make any sense to incorporate these features into Nuxt?

Hi,
Nuxt-Modules will be available in the next release and will give you the opportunity to add such functionality to Nuxt.

authors: alexchopin alidcastano


text:
PostCSS 8

Is your feature request related to a problem? Please describe.
PostCSS 8 came with a new plugin API. Right now Nuxt.js users can use new PostCSS plugins because Nuxt.js uses PostCSS 7.
Describe the solution you'd like
Update PostCSS from ^7.0.0 to ^8.0.0
Additional context
PostCSS 8 changelog
The only breaking changes important for Nuxt.js is dropping Node.js 6 and 8 support.

Hi @ai thanks for creating issue. We also planned doing upgrade. All dependencies dropped Node.js 8 support are currently locked for nuxt 2 to avoid breaking changes however seems for longer term it would be best to bump them in a semver-minor and notify users.

Still not works?

それでも動作しませんか？

postcss-nested worked for me when I lowered the version.

How is this still not merged? Postcss8 is out for half a year almost and most of plugins are not working with older versions. Making our projects hard to maintain.

@gapipro nuxt v2.15.0 has been released which includes postcss v8 support.
NOTE: postcss-preset-env is disabled in v8 config as it doesn't support postcss v8 for now, so please install all below dependencies explicitly.
yarn add --dev css-loader@^5.0.0 postcss@^8.1.10 postcss-import@^13.0.0 postcss-loader@^4.1.0 postcss-url@^10.1.1
# or
npm i --save-dev css-loader@^5.0.0 postcss@^8.1.10 postcss-import@^13.0.0 postcss-loader@^4.1.0 postcss-url@^10.1.1

@clarkdo How is this not mentioned anywhere? You literally saved me after spending 2 hours investigating CI issues.

Sorry, I’ll put it on release note

Is there a reason why this ticket is still open?

@simllll Yes. Nuxt still uses PostCss 7 as we're waiting for preset -env support. But Nuxt does support PostCss 8 if installed manually.

Please, keep this one opened until a proper support will land from postcss-preset -env support

Just published a module to make postcss8 opting-in process easier in the meantime: https://github.com/pi0/nuxt-postcss8

postcss8 support is finally stable with nuxt>=2.15.3 and nuxt/postcss8 module which uses autoprefixer instead of postcss-preset-env.
postcss8 for nuxt2 will probably always remain opt-in due to plugin breaking changes and env => autoprefixer change. But modules like tailwindcss can enforce using v8 to make it seamless for end-users. Will keep an eye on changes to reflect in nuxt/postcss8 module.
@ai Would you please help updating wiki page

Hi @pi0, this line still results on a warning when using the new nuxt/postcss8 module, not a big deal but kind of misleading:
https://github.com/nuxt/nuxt.js/blob/f08f4efcde7bc174fd9b68a2a5a785d504659391/packages/cli/src/utils/dependencies.js#L6

As @snake575 already mentioned. When using nuxt/postcss8 you still get the following warning.
 WARN  postcss@8.2.8 is installed but ^7.0.32 is expected

I tried to fix it, only to find out that this is expected behavior now.

postcss8 warning is removed for nuxt-edge and will be removed for next release of nuxt (via #8996)

If you've upgraded to @nuxtjs/tailwindcss to v4.x, be sure to upgrade @fullhuman/postcss-purgecss to v4 to use PostCSS v8.x with nuxtjs v2.15+.

postcss8 support is finally stable with nuxt>=2.15.3 and nuxt/postcss8 module which uses autoprefixer instead of postcss-preset-env (issue moved to nuxt/postcss8#4 to check possibility of using preset-env again)
Remaining opt-in of postcss8 for nuxt2 depends on plugin breaking changes. But is likely to be always opt-in. But modules like tailwindcss can enforce using v8 to make it seamless for end-users. Will keep an eye on changes to reflect in nuxt/postcss8 module.
@ai Would you please help updating wiki page?

I'm still getting the vulnerabilities warnings even though:

I've installed the nuxt/postcss8

npm i --save-dev css-loader@^5.0.0 postcss@^8.1.10 postcss-import@^13.0.0 postcss-loader@^4.1.0 postcss-url@^10.1.1

npm ls postcss would give me following tree:
├─┬ @nuxt/postcss8@1.1.3
│ ├─┬ css-loader@5.2.6
│ │ └── postcss@8.3.0  deduped
│ └── postcss@8.3.0
├─┬ css-loader@5.2.6
│ └── postcss@8.3.0  deduped
├─┬ nuxt@2.15.6
│ └─┬ @nuxt/webpack@2.15.6
│   ├─┬ css-loader@4.3.0
│   │ ├─┬ icss-utils@4.1.1
│   │ │ └── postcss@7.0.35  deduped
│   │ ├── postcss@7.0.35  deduped
│   │ ├─┬ postcss-modules-extract-imports@2.0.0
│   │ │ └── postcss@7.0.35  deduped
│   │ ├─┬ postcss-modules-local-by-default@3.0.3
│   │ │ └── postcss@7.0.35  deduped
│   │ ├─┬ postcss-modules-scope@2.2.0
│   │ │ └── postcss@7.0.35  deduped
│   │ └─┬ postcss-modules-values@3.0.0
│   │   └── postcss@7.0.35  deduped
│   ├─┬ cssnano@4.1.11
│   │ ├─┬ cssnano-preset-default@4.0.8
│   │ │ ├─┬ css-declaration-sorter@4.0.1
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ cssnano-util-raw-cache@4.0.1
│   │ │ │ └── postcss@7.0.35
│   │ │ ├── postcss@7.0.35
│   │ │ ├─┬ postcss-calc@7.0.5
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-colormin@4.0.3
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-convert-values@4.0.1
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-discard-comments@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-discard-duplicates@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-discard-empty@4.0.1
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-discard-overridden@4.0.1
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-merge-longhand@4.0.11
│   │ │ │ ├── postcss@7.0.35
│   │ │ │ └─┬ stylehacks@4.0.3
│   │ │ │   └── postcss@7.0.35
│   │ │ ├─┬ postcss-merge-rules@4.0.3
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-minify-font-values@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-minify-gradients@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-minify-params@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-minify-selectors@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-normalize-charset@4.0.1
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-normalize-display-values@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-normalize-positions@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-normalize-repeat-style@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-normalize-string@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-normalize-timing-functions@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-normalize-unicode@4.0.1
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-normalize-url@4.0.1
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-normalize-whitespace@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-ordered-values@4.1.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-reduce-initial@4.0.3
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-reduce-transforms@4.0.2
│   │ │ │ └── postcss@7.0.35
│   │ │ ├─┬ postcss-svgo@4.0.3
│   │ │ │ └── postcss@7.0.35
│   │ │ └─┬ postcss-unique-selectors@4.0.1
│   │ │   └── postcss@7.0.35
│   │ └── postcss@7.0.35
│   ├── postcss@7.0.35
│   ├─┬ postcss-import@12.0.1
│   │ └── postcss@7.0.35  deduped
│   ├─┬ postcss-loader@3.0.0
│   │ └── postcss@7.0.35  deduped
│   ├─┬ postcss-preset-env@6.7.0
│   │ ├─┬ autoprefixer@9.8.6
│   │ │ └── postcss@7.0.35
│   │ ├─┬ css-blank-pseudo@0.1.4
│   │ │ └── postcss@7.0.35
│   │ ├─┬ css-has-pseudo@0.10.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ css-prefers-color-scheme@3.1.1
│   │ │ └── postcss@7.0.35
│   │ ├── postcss@7.0.35
│   │ ├─┬ postcss-attribute-case-insensitive@4.0.2
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-color-functional-notation@2.0.1
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-color-gray@5.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-color-hex-alpha@5.0.3
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-color-mod-function@3.0.3
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-color-rebeccapurple@4.0.1
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-custom-media@7.0.8
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-custom-properties@8.0.11
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-custom-selectors@5.1.2
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-dir-pseudo-class@5.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-double-position-gradients@1.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-env-function@2.0.2
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-focus-visible@4.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-focus-within@3.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-font-variant@4.0.1
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-gap-properties@2.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-image-set-function@3.0.1
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-initial@3.0.4
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-lab-function@2.0.1
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-logical@3.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-media-minmax@4.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-nesting@7.0.1
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-overflow-shorthand@2.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-page-break@2.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-place@4.0.1
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-pseudo-class-any-link@6.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-replace-overflow-wrap@3.0.0
│   │ │ └── postcss@7.0.35
│   │ ├─┬ postcss-selector-matches@4.0.0
│   │ │ └── postcss@7.0.35
│   │ └─┬ postcss-selector-not@4.0.1
│   │   └── postcss@7.0.35
│   ├─┬ postcss-url@8.0.0
│   │ └── postcss@7.0.35  deduped
│   └─┬ vue-loader@15.9.7
│     └─┬ @vue/component-compiler-utils@3.2.0
│       └── postcss@7.0.35
└── postcss@8.3.0

@ai Would you please help updating wiki page?

Done

postcss-preset-env does not support PostCSS v8. See https://github.com/csstools/postcss-preset-env/issues/191 and https://github.com/csstools/postcss-preset-env/releases/tag/7.0.0.
So Nuxt v2 could now drop support for PostCSS v7 with these changes; making the manual workarounds and https://github.com/nuxt/postcss8 obsolete, right?

Please use nuxt/postcss8 module for postcss8 with nuxt 2.

authors: AndrewBogdanovTSS FarhanShares FloEdelmann MartinMa ai clarkdo danielroe gapipro imShara infinity899 janvorisek pi0 shou-kato simllll snake575


text:
Pages are created twice when SSR is false and splitChunks layouts is true

Versions

nuxt: v2.14.5, v2.14.6, v2.14.7
node: v12.x.x

Reproduction
The bug can be reproduced at the following codesandbox:
https://codesandbox.io/s/cool-water-vpncu?file=/nuxt.config.js

Additional Details

nuxt.config.js:
export default {
  ssr: false,

  build: {
    splitChunks: {
      layouts: true
    }
  }
};

Steps to reproduce

Configure nuxt as shown in the details above
Log something in the created lifecycle hook of any page.
Open the console and reload the page

What is Expected?
The page component is created only once and only one message should be logged in the console.
What is actually happening?
The page is created twice and 2 logs are printed
Observations
Not sure if it's of any help but the first time the page is created this.$nuxt.layoutName is an empty string.

same problem,but i don't know the reason,and you let me know,thanks

I have same problem, does anyone know how to fix it?

authors: imfaber nakaumin ragnaroks


text:
Babel "loose" option error spamming in console on fresh project

Versions

nuxt: v2.15.4
node: v14

Reproduction
Just make a new project on CodeSandbox and you'll see the error.
Here is one I just made: https://codesandbox.io/s/serene-thunder-yl6rq

Steps to reproduce

Make a new Nuxt project.
Run it.
Look at the console.

What is Expected?
No random warnings.
What is actually happening?
The warning...
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
	["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.

...is spammed over and over again.

how to fix this with npm

I fixed this by adding babel setting to the build section:
build: {
    **babel: {
      plugins: [['@babel/plugin-proposal-private-methods', { loose: true }]],
    },**
  },

to the nuxt.config.js file.
It removes the warning, I do not have a clue what it does under the hood.

I'm having this problem as well. I'm not even using babel, unless nuxt or another packages uses it?

@rickalex21 You will be in for an extremely bumpy and information dense ride. Babeljs has been part of many javascript build tooling for a very long time and therefor shouldn't be a surprise for any frontend developer.

I'm having this problem as well. I'm not even using babel, unless nuxt or another packages uses it?

In short, this is what the Babel website says about itself:

"Babel is a toolchain that is mainly used to convert ECMAScript 2015+ code into a backwards compatible version of JavaScript in current and older browsers or environments."

@xtrasmal Thanks for the info. I wasn't having these problems in hugo. I started using vuepress and so far so good, no errors or warnings.

/cc @clarkdo

The warning will be fixed in https://github.com/nuxt/nuxt.js/pull/9232.

Ahh im not the only one, i'm trying to update :P thanks guys

@pi0 @clarkdo I created a new project by running npx create-nuxt-app just now, and then when I ran npm run dev, I was shown this message.
 WARN  Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
        ["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.

I ultimately fixed it by running npm i @babel/core@7.13.15 @babel/preset-env@7.13.15, but I am unsure if #9232 squared this away unless I'm missing something.

@heyshadowsmith The fix has not been released yet, that's why @pi0 reopened this issue.

Im also encounter this problem,.
I was just deleted the node_modules directory, and package-lock.json,.
then npm install again,..
In running "npm run dev" it always shows the warning.

Im also encounter this problem,.
I was just deleted the node_modules directory, and package-lock.json,.
then npm install again,..
In running "npm run dev" it always shows the warning.

In nuxt.config.js
build: {
  babel: {
    plugins: [['@babel/plugin-proposal-private-methods', { loose: true }]],
  },
},

I see that there is a fix that has not been released yet however my nuxt projects are actually not running now that I'm getting these sudden console errors. They are just loading and hanging in a loading state. From earlier comments some people seem to still be able to run their projects. Could this be a seperate issue for me?

Also if I add the plugin: [['@babel/plugin-proposal-private-methods', { loose: true }]], to my nuxt config I get the following error:   Error: Failed to load config "developit" to extend from.

Im also encounter this problem,.
I was just deleted the node_modules directory, and package-lock.json,.
then npm install again,..
In running "npm run dev" it always shows the warning.

In nuxt.config.js
build: {
  babel: {
    plugins: [['@babel/plugin-proposal-private-methods', { loose: true }]],
  },
},

Thank you, it worked for my project 😊

@pi0 , Having same issue after upgrading to 2.15.7,  but found this work for me. https://github.com/babel/babel/issues/11622#issuecomment-638609015

@pi0  I am facing the same issue, just created a project with nuxt: v2.15.7

@Quineone Can you provide a reproducible repo ?

I wonder if this resurfaced somehow as I've seen this happening just yesterday in a repo that only has the latest dependencies.
You could try on https://codesandbox.io/s/nuxt-nuxtjsi18n-base-template-2szv3.
Export it and try locally. You can even delete the lock file and node_modules and re-test.

@clarkdo Here's one https://github.com/bhpcv252/nuxt-project.
Just created it using npx create-nuxt-app nuxt-project

Facing the same issue.

Thanks, I’ll look into it

@bhpcv252
// Build Configuration: https://go.nuxtjs.dev/config-build
  build: {
    babel: {
      plugins: [['@babel/plugin-proposal-private-property-in-object', { loose: true }]],
    }
  }

Fixes the issue for me for time being.

This will be fixed in https://github.com/nuxt/nuxt.js/pull/9631.

This will be fixed in #9631.

Ah yes, victory!

https://www.linkedin.com/pulse/nuxtjs-warn-though-loose-option-set-false-your-babelpreset-env-/

// Build Configuration: https://nuxtjs.org/docs/2.x/configuration-glossary/configuration-build
build: {
babel: {
plugins: [['@babel/plugin-proposal-private-property-in-object', { loose: true }]],
}
}

thnaks it also works for me
"resolutions": {   "@babel/core": "7.13.15",   "@babel/preset-env": "7.13.15" }

welcome
On Wed, Aug 11, 2021 at 2:56 PM er@ @.***> wrote:

thnaks it also works for me
"resolutions": { @./core": "7.13.15", @./preset-env": "7.13.15" }
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt.js/issues/9224#issuecomment-896636001, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AI7M5XWXHQ7HM72ME5GCN63T4I3L7ANCNFSM434QTNGQ
.

--
Thanks & Best Regards
Md Lemon Patwari
https://lemonpatwari.com https://lemonpatwari.com/
Web Apps Developer
+880 1763 053 987, +880 1521 424 060

One solution worked on Linux, a different in Windows, so I rolled them both in since I code at work on Windows and the rest of the time I'm on Linux;
    babel: {       plugins: [         ['@babel/plugin-proposal-private-property-in-object', { loose: true }],         ['@babel/plugin-proposal-private-methods', { loose: true }]       ]     },

Hi, in the version v2.15.8 this has worked:
babel: {       plugins: [         '@babel/plugin-proposal-class-properties',         '@babel/plugin-proposal-private-methods',         '@babel/plugin-proposal-private-property-in-object'       ]     }

Hi, in the version v2.15.8 this has worked:
babel: { plugins: [ '@babel/plugin-proposal-class-properties', '@babel/plugin-proposal-private-methods', '@babel/plugin-proposal-private-property-in-object' ] }

Doesn't work either ;(
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error: Cannot find module '@babel/plugin-proposal-private-property-in-object'

With yarn, please pin your babel deps manually in your package.json, then use yarn install again:
"resolutions": {
  "@babel/core": "7.13.15",
  "@babel/preset-env": "7.13.15"
}

With npm, add these as dev deps (with the same versions).

Thanks alot. This worked

authors: AaronBeaudoin AbingPj FalseHuman JLBlueDom Quineone bhpcv252 c2oc clarkdo codingotaku devzom eraloop escael hardydex heyshadowsmith kgrosvenor lemonpatwari nvrooij pi0 rchl rexarvind rickalex21 rob-tech therealemino xtrasmal


text:
fix(core): use require.resolve instead of Module internals

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Is there any reason to not use require.resolve but rather a private module function? We use Bazel as our build tool to call nuxt and it implements a custom module resolution. Using this private method currently does not work, but using require.resolve does. Would be great to get this in if there is no specific reason to use this private method.
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Historically coming from #1136. It seems require.resolve also accepts second paths param so looks a valid fix.

@pi0 I did some local testing and it seems the returned errors are different from require.resolve, so this should hopefully fix it.

@pi0 It looks like that paths in _resolveFilename and resolve are different.
paths in _resolveFilename is parent, in resolve is module location.
https://github.com/nodejs/node/blob/master/lib/internal/modules/cjs/helpers.js#L21

Good point @clarkdo, but I guess the main question is, does it still achieve the same thing, or is it maybe even the more correct thing to do?

@Globegitter You're right, options.paths in resolve will be converted to fake parent in _resolveFilename, but I'm not sure why the error thrown is not MODULE_NOT_FOUND, I need more investigation for avoiding unexpected behaviour.

@clarkdo Yeah that is strange indeed - but at least all the tests are passing now, so that is something. In my local testing error.code was not set in most of the cases, not sure why that is the case. Anyway, I can understand that you need more time to investiage.

Codecov Report

Merging #5796 into dev will decrease coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev    #5796      +/-   ##
==========================================
- Coverage   95.69%   95.66%   -0.04%
==========================================
  Files          82       82
  Lines        2674     2675       +1
  Branches      685      686       +1
==========================================
  Hits         2559     2559
- Misses         97       98       +1
  Partials       18       18

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.54% <100%> (+0.01%)
:arrow_up:

#unit
92.63% <100%> (-0.04%)
:arrow_down:

Impacted Files
Coverage Δ

packages/core/src/resolver.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderer.js
93.49% <0%> (-0.82%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e75d65b...dbb9b73. Read the comment docs.

@Globegitter Error is from https://github.com/facebook/jest/blob/master/packages/jest-runtime/src/index.ts#L650-L654 which doesn't set code, so it only happens in jest.

Codecov Report

Merging #5796 into dev will decrease coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev    #5796      +/-   ##
==========================================
- Coverage   95.69%   95.66%   -0.04%
==========================================
  Files          82       82
  Lines        2674     2677       +3
  Branches      685      686       +1
==========================================
+ Hits         2559     2561       +2
- Misses         97       98       +1
  Partials       18       18

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.54% <100%> (+0.01%)
:arrow_up:

#unit
92.64% <100%> (-0.03%)
:arrow_down:

Impacted Files
Coverage Δ

packages/core/src/resolver.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderer.js
93.49% <0%> (-0.82%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e75d65b...d3f19aa. Read the comment docs.

source: gharchive/pull-request

authors: Globegitter clarkdo codecov-io pi0


text:
Modify a scss subfile cause a full app reload (hmr)

Hello there, and thanks for you work on Nuxt 3!
Environment

Operating System: Windows_NT
Node Version:     v16.15.1
Nuxt Version:     3.1.1
Nitro Version:    2.0.0
Package Manager:  yarn@1.22.5
Builder:          vite
User Config:      vite, typescript, image, modules, plugins, pinia, apollo
Runtime Modules:  @pinia/nuxt@0.4.5, @pinia-plugin-persistedstate/nuxt@1.0.0, @nuxt/image-edge@1.0.0-27809804.194d2d6, @nuxtjs/apollo@5.0.0-alpha.4
Build Modules:    -

package.json
"devDependencies": {
    "@nuxt/image-edge": "^1.0.0-27769790.4b27db3",
    "@nuxtjs/apollo": "^5.0.0-alpha.4",
    "nuxt": "^3.1.1",
    "sass": "^1.57.1"
  },

Reproduction
can't reproduce the bug on codesandbox...
Describe the bug
I have this structure:
assets/
  styles/
    _layout.scss
    styles.scss

In dev mode (nuxt dev):

when I edit and save the style.scss file, I have instant css only reload ✔
but when I edit and save the _layout.scss, it causes a full app reload (but here is the joke: not always...) ❌

I can't reproduce the case, because it's seems to be randomly...
I tried to remove every scss dependency one by one, and sometimes it repairs the hmr, sometimes not, this drives me crazy!!!
I hope I'll find some help here, thanks!
Additional context
I tried to import the scss file through the nuxt.config.ts method:
export default defineNuxtConfig({
  css: [
    "@/assets/styles/styles.scss"
  ]
})

OR through the app.vue method, but it's the same problem:
<script lang="ts">
  import "@/assets/styles/styles.scss";
</script>

BUT, when I remove the import "@/assets/styles/styles.scss";, launch the nuxt dev command, and then add import "@/assets/styles/styles.scss";, it's working... (but i'll have to do this everytime and it's not a solution)
So I don't understand.
Logs
No response

Hm, I have also declared a scss file inside my nuxt.config css-property. Instant HMR. Create a fresh nuxt app locally and see if this happens there too.

After some research, here are some details:

the HMR is working correctly when the modifications are made on the style.scss file
but if changes are made on a imported file, like _layout.scss (who is imported in style.scss), then it causes a full app reload

I'm gonna edit my thread.

instant HMR for me also with imported _partials.
Could you provide a reproduction? 🙏🏻

authors: dsvgl maximelebreton

repo: nuxt/nuxt


text:
Nuxt3 .server (island) components fail to render on soft navigation if they have different props on pages

Environment
Works in any environment, including StackBlitz:
- Operating System: Linux
- Node Version:     v16.20.0
- Nuxt Version:     3.7.1
- CLI Version:      3.7.3
- Nitro Version:    2.6.2
- Package Manager:  npm@9.4.2
- Builder:          -
- User Config:      experimental
- Runtime Modules:  -
- Build Modules:    -

Reproduction
Please refer to:
https://stackblitz.com/edit/github-ydxe3t?file=pages%2Findex.vue

Do nuxt generate and npx serve .output/public.
CLick the link 'Go to page with scoped styles'
Note the 404 in console on click to the link and absence of the component
Reload the page
Note the component was loaded normally
Remove scoped attribute from style tag in pageWithScopedStyles.vue and repeat the excercise

Describe the bug
Apparently because scoped styles in Vue are implemented using attributes and the server components are rendered based on attribute values, server components in some instances will break (the client will request a non-existing URL of __nuxt_island/whatever_id, leading to a 404. This will lead to the component not being displayed.
The sufficient conditions for the reproduction are following:

There is a server component used on two separate pages
It's not used directly, but through a third component (I used a wrapper) which uses this component as root
It has a prop that is different on these pages (I injected the route, I suppose it's also possible that a state variable may be passed as a prop

This is not reproduced in dev, only if the site is statically generated using nuxt generate and the client navigates to the page which uses scoped styles using soft navigation, e.g. <NuxtLink />
I'm not certain what causes the bug.
Additional context
I know this might sound like an edge case but I arrived to this bug in a real-world scenario and I imagine this could be an issue for example  for component library creators who want to use .server components (llike myself). An easy enough workaround is to avoid using it as a root in the wrapper but I'm sure there are also other unforeseen scenarios that might trigger this problem.
The fact is, it works OK in dev, but breaks during SSG.
Logs
No response

Quick follow-up. The issue is not reproduced if using  instead of a .server component, so that's one reasonable workaround for the time being

Yes, this is an interesting one for sure. Any thoughts @huang-julien?

Quite strange, i'll take a look 👀 probably a bug at build time with the loader.

I think the issue is that any attributes end up as props, and so data attribute added by vue becomes a prop. We might be able to explicitly ignore? Or you may have a better idea.

Yes, that's the issue. I'm looking at if we can ignore data attributes within createServerComponent without having to manually ignore data-v- attributes

authors: arsengoian danielroe huang-julien


text:
Different error data in SSR and CSR

Environment

Operating System: Linux
Node Version:     v18.18.0
Nuxt Version:     3.10.3
CLI Version:      3.10.1
Nitro Version:    2.8.1
Package Manager:  npm@10.2.3
Builder:          -
User Config:      devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-b1eyhh-m1rujh?file=server%2Fapi%2Ffoo.ts,pages%2Ffoo.vue
Describe the bug
I throw custom error in the API event handler /api/foo, but useFetch returns incorrect error data in CSR.

Open Foo page first time (SSR) -> statusMessage: 'Custom Not Found'
Go to Index and then back to Foo (CSR) -> statusMessage: 'Not Found'

As you see, statusMessages are different. Looks like createFetchError in ofetch takes different ctx data in SSR and CSR.
Additional context
No response
Logs
No response

Related issue and reasoning: https://github.com/nuxt/nuxt/issues/24693#issuecomment-1850786194
So error.data is what you're looking for.
I think this could be worth adding to the documentation though. Let's see what others think

It can be different depending on the platform, but I think it shouldn't be different between SSR and CSR on the same platform.

@warflash

So error.data is what you're looking for.

But why? I found several issues explaining that you should use error.data.statusMessage instead of error.statusMessage. But none of them explain why.
As I understand, the error.statusMessage is the HTTP Protocol status text also known as reason phrase., returned together with the HTTP status code in the HTTP response status line. While error.data.statusMessage is just a JSON field of the HTTP response payload. Please correct me if I'm wrong.
In DEV mode the DEV server response looks like this:
HTTP/1.1 <statusCode from createError(...)> <statusMessage from createError(...)>

E.g. for an error like this:
throw createError({
    statusCode: 403,
    statusMessage: 'USER_IS_NOT_A_MEMBER',
})

The response will be like this:
HTTP/1.1 403 USER_IS_NOT_A_MEMBER
...headers...

{"url":"...","statusCode":403,"statusMessage":"USER_IS_NOT_A_MEMBER"}

But in PROD mode the response of the server is like this:
HTTP/3 403
...headers...

{"url":"...","statusCode":403,"statusMessage":"USER_IS_NOT_A_MEMBER"}

As you can see the HTTP response status line doesn't contain status text. Probably in my case this is not a Nuxt fail, but a Google Load Balancer proxy fail (I suspect the LB removes the response status text, but I'm not sure - can't find it in the docs).
But, even if it is Load Balancer's fail, we should accept that this is pretty common for a load balancers/proxies to mess with the HTTP protocol level status line. So, it would be wise to not rely on this when the response is converted back to FetchError object. When I'm calling throw createError({ statusCode: 403, statusMessage: 'USER_IS_NOT_A_MEMBER' }) I expect that on the client I will receive error.statusMessage that is equal to USER_IS_NOT_A_MEMBER. The current behavior is very confusing and error-prone.
Can we just deserialize statusMessage from the response body instead of relying on the HTTP Protocol status line? This will be much more reliable as it doesn't involve relying on the HTTP Protocol level status text (reason phrase), that is optional by the HTTP Protocol RFC and is often removed/normalized by production proxies.
From the RFC:

The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.

(emphasize is mine)
The RFC doesn't say that the Reason-Phrase shouldn't be examined by the client, but it still states the main reason for the Reason-Phrase to exist: for the human user. And the established practices from the last 20 years are like this. That is why, I think, popular proxy implementations and cloud providers are feeling free to mess with the Reason-Phrase. They do not expect it to be used for the app logic.
If it is not possible to deserialize error.statusMessage from the response body, then I think at the very minimum the Nuxt documentation should explain what statusMessage of createError parameter object is (how it is transferred and how to access it on the client) and warn that we should not rely on the value of this field on the client. I think, the docs should discourage to use this field of the error object and encourage to use the error.data instead, if it is not possible to deserialize the error.statusMessage from the response body.

authors: enkot warflash xak2000


text:
Extremely slow due to the Nuxt Modules!!! I even can not bear that!

Environment
Nuxt project info:                                                                                6:37:53 PM

Operating System: Linux
Node Version:     v20.15.1
Nuxt Version:     3.14.159
CLI Version:      3.15.0
Nitro Version:    2.10.4
Package Manager:  yarn@1.22.22
Builder:          -
User Config:      default
Runtime Modules:  @nuxt/ui@2.19.2, nuxt-monaco-editor@1.3.1, @element-plus/nuxt@1.1.0
Build Modules:    -

Reproduction
This is my nuxt.config.js:
export default defineNuxtConfig({
	devtools: { enabled: true },
	ssr:true,
	devServer:{
		host:"0.0.0.0",
		port:8001,
	},
	modules: ["@nuxt/ui", "nuxt-monaco-editor", '@element-plus/nuxt'],
	plugins:[{
		src:"~/plugins/router.js",
		ssr:false,
	}],
	alias: {
		'css':"/assets/css",
		'font':"/assets/font",
		"comps":"/components",
		"pages":"/pages"
	},
	css:["css/index.css"],
	compatibilityDate: "2024-08-05",
})

Very simple, but I found that in the DEV mode, devServer will load the modules' file (in the node_modules) for many times repeatly!
These 3 modules generated about 2k js files needing to load, which spend about 2minutes to load a page, but when I just modify a little bit part of my code(or just wait for some time without doing anything), the version of the js files changed, so I need to load them again!

Only the js files for the 3 modules would be loaded for many times, others wouldn't.
Describe the bug
Like the above, in the loading time, I could do nothing but waiting.There is no response after clicking the link, button or other item.
Additional context
No response
Logs

Hey! This is normal in dev mode due to Vite serving everything unbundled.
It might be worth figuring out which module is causing issues you encounter (+ using Nuxt UI and Element Plus might not be the best idea) & check out https://github.com/nuxt/nuxt/issues/26211 as well.
As this is not a Nuxt issue per sé, I'll close this issue.

authors: Eriktse manniL


text:
Sass directive @debug not printing anything when used. Nor does @warn.

Version
v2.9.1
Reproduction link
/
Steps to reproduce

Configure the Sass pre-processor.
Write in a used .scss file: @debug 'I love Nuxt'
Look for an output in the terminal.

What is expected ?
To see 'I love Nuxt' printed out in the Terminal.
What is actually happening?
Nothing shows.
Additional comments?
The same goes for @warn directive.

This bug report is available on Nuxt community (#c9934)

This issue is still going on. I am unable to use @debug and other notification functions in nuxt

Confirm, unable to debug anything.

Bumped into this issue trying to use @debug, no output provided.

I have the same error and couldn't fix the beast even after wandering in web jangle.
$primary-color: #1919f9;
@debug $primary-color;
There is no output show of the above code.

authors: Aamirpare Anton-Evstigneev IvanGatsinski JDIZM mevbg


text:
Receiving "command not found" on configuration

Tested in my shell on Xubuntu 14.04:
♥ mhausman@Quasit:~ ‽ thefuck --alias
alias fuck='TF_CMD=$(TF_ALIAS=fuck PYTHONIOENCODING=utf-8 TF_SHELL_ALIASES=$(alias) thefuck $(fc -ln -1)) && eval $TF_CMD && history -s $TF_CMD'
♥ mhausman@Quasit:~ ‽ eval "$(thefuck --alias)"
: command not found

Note that it functions oddly afterwards. For instance, after running I did the following:
♥ mhausman@Quasit:~ ‽ gdit
No command 'gdit' found, did you mean:
 Command 'dgit' from package 'dgit' (universe)
 Command 'git' from package 'git' (main)
 Command 'gedit' from package 'gedit' (main)
 Command 'gdis' from package 'gdis' (universe)
 Command 'edit' from package 'mime-support' (main)
gdit: command not found
♥ mhausman@Quasit:~ ‽ fuck
gedit [enter/↑/↓/ctrl+c]

It looks like it's working. But when I hit enter, the command it actually ran was gedit ^[[0m. I'm not sure if that's related, but it seemed worth mentioning.

So I guess this is just more of the weird whitespace handling. We can add xfce-terminal to the list of terminals that aren't being handled properly.
♥ mhausman:~/<snip> ‽ checkout master
checkout: command not found
♥ mhausman:~/<snip> ‽ fuck
git checkout master [enter/↑/↓/ctrl+c]
error: pathspec '' did not match any file(s) known to git.

Hi! Please paste the output of the two commands below:
thefuck --version

python -c 'from thefuck.shells import shell; print(shell.__class__)'

Thanks!

♥ mhausman:~ ‽ thefuck --version
The Fuck 3.9 using Python 2.7.6
♥ mhausman:~ ‽ python -c 'from thefuck.shells import shell; print(shell.__class__)'
<class 'thefuck.shells.bash.Bash'>

@mdhausman, this is what I got on a fresh Xubuntu 14.04 install:

What is your Bash version? And can you share your ~/.bashrc file?
Thanks!

Also germane to the discussion:
vagrant@vagrant-VBox:~$ apt-cache show xfce4-terminal | grep -E 'Pa|In|Ve'
Package: xfce4-terminal
Installed-Size: 2071
Version: 0.6.3-1ubuntu1

♥ mhausman:~ ‽ bash --version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
♥ mhausman:~ ‽ apt-cache show xfce4-terminal | grep -E 'Pa|In|Ve'
Package: xfce4-terminal
Installed-Size: 2071
Version: 0.6.3-1ubuntu1

Thanks for that information. How about your .bashrc? Or the script that
evals the fuck function. Thanks.
Em 20/05/2016 18:53, "Maura Hausman" notifications@github.com escreveu:

♥ mhausman:~ ‽ bash --version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
♥ mhausman:~ ‽ apt-cache show xfce4-terminal | grep -E 'Pa|In|Ve'
Package: xfce4-terminal
Installed-Size: 2071
Version: 0.6.3-1ubuntu1
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/nvbn/thefuck/issues/499#issuecomment-220727346

I am getting the same problem in both Gnome terminal and XFCE terminal (both on Mint). The problem occurred after I edited by /etc/environment, which contains the PATH variable.
Also: we've got a duplicate of this issue here (#502).

authors: ACinnamonUserInUK mdhausman scorphus

repo: nvbn/thefuck

license: mit

license_source: bigquery


text:
🛑 PufferAI HPC Portal is down

In b003f98, PufferAI HPC Portal (https://hpc.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PufferAI HPC Portal is back up in 93c018f.

repo: nvgsg/lab-upptime


text:
🛑 NVIDIA AI Enterprise Hub is down

In e4802cd, NVIDIA AI Enterprise Hub (https://nvaie.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NVIDIA AI Enterprise Hub is back up in 4223934.


text:
🛑 Lab Catalog is down

In 8bc586a, Lab Catalog (https://catalog.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Lab Catalog is back up in 830cdc9.


text:
🛑 NVIDIA AI Enterprise Hub is down

In 746b0ef, NVIDIA AI Enterprise Hub (https://nvaie.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NVIDIA AI Enterprise Hub is back up in 3861752.


text:
🛑 Kubeflow ML Platform is down

In b8c7959, Kubeflow ML Platform (https://kubeflow.lab.novaglobal.com.sg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kubeflow ML Platform is back up in 3a00cf8.


text:
Need help on open file flow

i want to open file with window picker if there are multiple window, just open if not. Tried to chain open_with_window_picker with open_drop but didn't work. Please advise how to achieve this flow.

If I understand you correctly, you are trying to a) if only one buffer, open file automatically, and b) if there are multiple windows other than neo-tree, use nvim-window-picker to select which window to open, right?
This should be the default behavior without any specific configuration so could you show me your current configuration?

@pysan3 i'm using alpha.nvim, open_with_window_picker not works if buffer is alpha.

Hi @Orgil,
I have tried my best to reproduce your problem but unfortunately had no luck.
Could you post your config and a screen record to elaborate the problem?

Tried to chain open_with_window_picker with open_drop but didn't work.

Besides, what do you mean by this?
At least I comprehended that as adding this code to neo-tree's codebase (since I don't think it's easy to achieve with custom commands. It is the easiest to use the use_window_picker function which is local to neo-tree codebase.)
With this modification, I have no issues opening with drop_with_window_picker even with alpha being one of the buffers.
Modified lua/neo-tree/sources/common/commands.lua
@@ -713,6 +713,11 @@ M.vsplit_with_window_picker = function(state, toggle_directory)
   open_with_cmd(state, "vsplit", toggle_directory, use_window_picker)
 end

+M.drop_with_window_picker = function(state, toggle_directory)
+  open_with_cmd(state, "drop", toggle_directory, use_window_picker)
+end
+
 M.show_help = function(state)
   help.show(state)
 end

@pysan3 i'm not sure why mine config doesn't work. i mapped like ["o"] = "open_with_window_picker", so as soon as open neovim it brings alpha.nvim as startup buffer. So i called :Neotree toggle which brings neotree. From there toggling folder works find but to open file with o doesn't work. However open_drop works fine.

@Orgil did you perhaps set nvim-window-picker to ignore the alpha.nvim buffer? You can see it in filter_rules.bo.filetypes of nvim-window-picker's config.

@nhat-vo that was it. i was misunderstanding that config and added alpha there previously. Thank you.

authors: Orgil nhat-vo pysan3


text:
Script Ansible installing NVM and Node LTS.

Script Ansible installing NVM and Node LTS.

- name: 'Git clone do NVM v0.34.0'
  git:
    repo: https://github.com/nvm-sh/nvm.git
    dest: ~/.nvm
    version: v0.34.0

- name: Exporta NVM_DIR
  shell: "{{ item }}"
  with_items:
    - echo 'export NVM_DIR="$HOME/.nvm"' >> ~/.bashrc
    - echo '[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"' >> ~/.bashrc
    - echo '[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"' >> ~/.bashrc
    - echo 'export NVM_DIR="$HOME/.nvm"' >> ~/.profile
    - echo '[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"' >> ~/.profile
    - echo '[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"' >> ~/.profile

    - name: Install node LTS
      shell: "source  ~/.nvm/nvm.sh && nvm install --lts"
      args:
        executable: /bin/bash

Please don't spam this as comments onto other issues.
What's the purpose of this issue?

I think, he points out that running nvm with ansible is a mess. You can't use bashrc, because it is not an interactive shell.  You cant use source because why the f... should you? There are countless of things on the internet about this!!!!

Can you elaborate? Why can’t you use source? nvm is a sourced shell function, so that’d be the only way to use it.
You don’t need an interactive shell; you can put the nvm sourcing lines in .profile.

I like to follow up, as I have a problem as well with nvm an Ansible. The OP did not mention a particular problem, so I won't hijack a thread off-topic.
The nvm installers adds 3 lines into the userś  *rc file. Think of managability of these entries: If those three lines change in the future, you'll have to identifiy the lines for sure etc.pp.
The Python venv's use a single source file: $HOME/...../bin/activate
It is easier to identify exactly this one line, e.g. on removable.
If the lines need to change, the installer / updater migrates the "active" file.
I suggest to create yet another three-line rc-file, that is sourced in by the user's rc file. You could add a command line option "--interactive" to enable the source of stuff useful for interactive shells.
The main problem for Ansible is, that it is cumbersome to have the shell-functions present. For Venvs there is a special Ansible module, which makes sure the "activate" file is sourced.
In order to develop such module it would easier, when there is one "central" file.

While that's true, I don't think the benefit would be sufficient to be worth the disruption.
Closing, since the OP never replied.

Can you please reply me with the utmost respect how do I access my balances
in github repos
On Mon, Oct 21, 2024, 2:45 AM vm7096659522886852v @.***>
wrote:

I like to follow up, as I have a problem as well with nvm an Ansible. The
OP did not mention a particular problem, so I won't hijack a thread
off-topic.
The nvm installers adds 3 lines into the userś *rc file. Think of
managability of these entries: If those three lines change in the future,
you'll have to identifiy the lines for sure etc.pp.
The Python venv's use a single source file: $HOME/...../bin/activate
It is easier to identify exactly this one line, e.g. on removable.
If the lines need to change, the installer / updater migrates the "active"
file.
I suggest to create yet another three-line rc-file, that is sourced in by
the user's rc file. You could add a command line option "--interactive" to
enable the source of stuff useful for interactive shells.
The main problem for Ansible is, that it is cumbersome to have the
shell-functions present. For Venvs there is a special Ansible module, which
makes sure the "activate" file is sourced.
In order to develop such module it would easier, when there is one
"central" file.
—
Reply to this email directly, view it on GitHub
https://github.com/nvm-sh/nvm/issues/2087#issuecomment-2426164058, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BHRRARV4F3ZEMHKKLGBS7DDZ4TEMBAVCNFSM6AAAAABQJX4YDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWGE3DIMBVHA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

authors: TafkaMax ljharb plsergio thearbinaut vm7096659522886852v

repo: nvm-sh/nvm


text:
How to uninstall nvm?

I want to uninstall nvm completely. Is there documentation on how to do this?

For additional info, nvm may be installed via Homebrew or npm. Check your installed packages for the proper way to remove the binary files.

@scott-joe nvm should never be installed via homebrew - it's entirely unsupported. See #469. In addition, the nvm on npm is NOT the correct one, and will not work anyways - see #304.

What's the reasoning for not hosting nvm on npm?

@trusktr it's not "reasoning", it's that it's a different project that's now deprecated. I've been given ownership of it, and at some point in the future (see #304), I'll replace it with something that bootstraps the proper nvm.

It might not make sense. It'd just be nice to uninstall it easily. Maybe it can prompt at the command like something like "This will uninstall versions of node installed by nvm too. Continue?".

Wait, I'm not even sure that's possible. Oh well, I was able to remove it manually any ways, and I can use Arch Linxu's pacman to see which files don't belong to any package and remove those too.

it's pretty simple. rm -rf $NVM_DIR and remove the two lines in your profile file.

@ljharb  it works

can we get an nvm uninstall command?

@chovy that would require modifying one or more of your profile files, otherwise it'd just be rm -rf "$NVM_DIR" - that's pretty destructive, and not something I'd want to encourage.
Disk space is cheap, so the best way to uninstall it is to simply disable it by removing the sourcing lines from your profile files - which has to be done manually.

I've removed the directory and I still can execute nvm from git bash, what going on?

@jcubic you may need to restart git bash and/or Windows. Sourced shell functions stay in memory even if the files are deleted.

step1 - check env:
[root@demo tatia]# echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/.nvm/versions/node/v6.2.2/bin

step2 (remove nvm env from envs):
export PATH=/usr/local/bin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

done.

@sconts to uninstall, yes. when installed, however, the nvm paths should be first, or else it won't work properly. (however, nvm unload  and nvm deactivate both remove it for you)

clear $NVM_DIR
rm -rf $NVM_DIR ~/.npm ~/.bower && unset NVM_DIR

@myisjon ~/.npm and ~/.bower are for npm and bower, respectively; you don't necessarily want to ~/.npm when removing nvm. (of course, you'll want to remove bower in every case)

How about adding this in README?

Please add uninstall instructions to the README. One preference for using package managers to install node or anything else is ease of removal. Should be explicitly defined somewhere the best practice in completely removing it...

One hard thing to remember is how nvm was installed in the first place. I thought I had used homebrew (glad I didn't), but I used wget instead. I wonder if there is a way to know afterwards how nvm was installed.
I ran into another issue and saw that issue which helped me understand things out.
See https://stackoverflow.com/questions/34718528/nvm-is-not-compatible-with-the-npm-config-prefix-option
See https://stackoverflow.com/a/54617989/2391795 for how to reinstall nvm

@Vadorequest If everything is in ~/.nvm then it is installed with the official installation script.

In addition to rm -rf /root/.nvm if someone accidentally installed nvm as 'root' and is trying to reinstall it as a user you might also want to remove the following lines from /root/.bashrc
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

Note tho that those lines are safe noops if you’ve deleted the dir.

@ljharb export NVM_DIR="$HOME/.nvm" this line in particular wasn't letting me install nvm as a user with wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash even after I deleted the nvm directory and reloaded my shell. I couldn't reboot the server though as it's Production.

hmm, I’m not sure why a root env var would persist in a non-root session, but fair enough.

@dorkmania You don’t have to reboot, just log in again (as non-root user, of course).

@FranklinYu maybe it was just CloudLinux acting weird but I couldn't reinstall even after closing my ssh connection, re-logging in to root and then changing to the user account; till I deleted that line. The script kept giving me a message along the lines of  $NVM_DIR set to "/root/.nvm" before stopping. (.nvm was already deleted)

@dorkmania You are not logging into the user account when you first login as root and switch user. The first user matters. Contact your cloud provider if they don’t provide direct access to non-root user login session, or this will bite you here and there.

@FranklinYu Makes sense.

rm -rf ~/.nvm
rm -rf ~/.npm
rm -rf ~/.bower

works like fine-wine!

step1 - check env:
[root@demo tatia]# echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/.nvm/versions/node/v6.2.2/bin

step2 (remove nvm env from envs):
export PATH=/usr/local/bin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

then, remove /root/.nvm/*
done.

Works like a charm!

step1 - check env:
[root@demo tatia]# echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/.nvm/versions/node/v6.2.2/bin

step2 (remove nvm env from envs):
export PATH=/usr/local/bin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

then, remove /root/.nvm/*
done.

Works like a charm!

It is very inconvenient way. First we need to remove directories and then we need to bother with cleaning up configs manually

It is very inconvenient way. First we need to remove directories and then we need to bother with cleaning up configs manually

@xahon it would be very dangerous to mess with your profile files. The most an nvm command could safely do is rm -rf $NVM_DIR, so you'd still end up running a single command, and then manually deleting 2-3 lines from a profile file.

@xahon it would be very dangerous to mess with your profile files. The most an nvm command could safely do is rm -rf $NVM_DIR, so you'd still end up running a single command, and then manually deleting 2-3 lines from a profile file.

@ljharb fzf has an utility to remove itself in a safe manner. So user can override NVM_DIR by some reason and it is not safe to do rm -rf $NVM_DIR too

@ljharb fzf has an utility to remove itself in a safe manner. So user can override NVM_DIR by some reason and it is not safe to do rm -rf $NVM_DIR too

It’s quite safe; and any user who overrides NVM_DIR would cause nvm to delete the overridden dir anyways, since that’s the only way nvm knows where it lives.
i can’t speak for fzf or any other tool; the current requirements are one rm command, and optionally deleting 2-3 lines from your profile file. There’s nowhere close to enough incremental value from an uninstall command to risk it.

It’s quite safe; and any user who overrides NVM_DIR would cause nvm to delete the overridden dir anyways, since that’s the only way nvm knows where it lives.
i can’t speak for fzf or any other tool; the current requirements are one rm command, and optionally deleting 2-3 lines from your profile file. There’s nowhere close to enough incremental value from an uninstall command to risk it.

ddddddddd

work for me in macos
rm -rf ~/.nvm
brew cleanup --prune-prefix

@mibamur There is no need for such emphasis in your comments. And it is probably better to use the $NVM_DIR variable, as not everyone has nvm installed in ~/.nvm.
Oneliner:
rm -rf $NVM_DIR ~/.npm ~/.bower

then restart your terminal and check🙂

I wrote a script for the nuclear option of blowing everything away. Yes it's destructive!
Also added option to install volta to manage tools.
https://docs.volta.sh/guide/#why-volta
If you're in an agreeable mood when you run the script you'll end up with node, npm, and nvm gone with volta installed instead.
https://github.com/av8ta/nuke-node

@jcubic you may need to restart git bash and/or Windows. Sourced shell functions stay in memory even if the files are deleted.

I restarted windows and this is still a problem.

@OkilyDokily please file a new issue, filling out the entire issue template, and we can work it out. (be sure you're using real nvm, and not nvm-windows, which is a different project)

@OkilyDokily please file a new issue, filling out the entire issue template, and we can work it out. (be sure you're using real nvm, and not nvm-windows, which is a different project)

I found the nvm folder in the app data roaming directory.

no one of above removed my nvm. No bash script for it?
i can't get rid of it!!

I have a bash script for it mentioned above @Barabba11 but it was marked as disruptive for some reason so I'm loathe to post it again.

@av8ta because it's not for removing nvm, it's for replacing nvm with a different tool. that's not helpful here.

@Barabba11 removing nvm is a two step process - rm -rf $NVM_DIR, and then optionally remove the nvm lines from your profile file.

@Barabba11 removing nvm is a two step process - rm -rf $NVM_DIR, and then optionally remove the nvm lines from your profile file.

Did't work, pobably because it was not properly configured in PATH, so I removed it under root folder and now I can installa Node Red. Thanks

Having nvm installed shouldn't interfere with any kind of system node, whether node red or otherwise. nvm deactivate or nvm use system should be sufficient to allow that to work.

and how to fine the $NVM_DIR .

@Feyem9 it’s an env var. By default it’ll be $HOME/.nvm, but you can just check its value.

nvm unload and its removed from shell

authors: Barabba11 CornerstoneII Feyem9 FranklinYu Maxlo27 MuhammadUmairMoosani OkilyDokily Vadorequest av8ta cdock1029 chovy dorkmania dutscher franklinyu jcubic ljharb lopeselio mehulkar michaeltyhuang myisjon sconts scott-joe shriraj20 trusktr xahon


text:
nvm install-latest-npm not install last compatible in node16

Operating system and version:
macos 15.5.2
nvm debug output:

nvm debug
nvm --version: v0.39.3
$TERM_PROGRAM: Hyper
$SHELL: /bin/zsh
$SHLVL: 1
whoami: 'codati'
${HOME}: /Users/codati
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: ${NVM_DIR}/versions/node/v16.20.2/bin:${HOME}/.pyenv/shims:/opt/local/bin:/opt/local/sbin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'zsh 5.9 (x86_64-apple-darwin22.0)'
uname -a: 'Darwin 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul 5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000 arm64'
checksum binary: 'shasum'
OS version: macOS 13.5.2 22G91
awk: /usr/bin/awk, awk version 20200816
curl: /opt/local/bin/curl, curl 8.3.0 (aarch64-apple-darwin22.6.0) libcurl/8.3.0 OpenSSL/3.1.3 zlib/1.3 brotli/1.0.9 zstd/1.5.5 libidn2/2.3.4 libpsl/0.21.2 (+libidn2/2.3.4) nghttp2/1.56.0
wget: /opt/homebrew/bin/wget, GNU Wget 1.21.4 compilé sur darwin22.4.0.
sed: /usr/bin/sed
cut: /usr/bin/cut
basename: /usr/bin/basename
rm: /bin/rm
mkdir: /bin/mkdir
xargs: /usr/bin/xargs
git: /usr/bin/git, git version 2.39.2 (Apple Git-143)
grep: /usr/bin/grep, grep (BSD grep, GNU compatible) 2.6.0-FreeBSD
nvm current: v16.20.2
which node: ${NVM_DIR}/versions/node/v16.20.2/bin/node
which iojs: iojs not found
which npm: ${NVM_DIR}/versions/node/v16.20.2/bin/npm
npm config get prefix: ${NVM_DIR}/versions/node/v16.20.2
npm root -g: ${NVM_DIR}/versions/node/v16.20.2/lib/node_modules

nvm ls output:

nvm ls
       v14.21.2
       v16.20.0
       v16.20.1
->     v16.20.2
default -> lts/gallium (-> v16.20.2)
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v16.20.2) (default)
stable -> 16.20 (-> v16.20.2) (default)
lts/* -> lts/hydrogen (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.12 (-> N/A)
lts/fermium -> v14.21.3 (-> N/A)
lts/gallium -> v16.20.2
lts/hydrogen -> v18.18.0 (-> N/A)

How did you install nvm?
script in readme
What steps did you perform?
nvm install-latest-npm

What happened?
nvm install-latest-npm
Attempting to upgrade to the latest working version of npm...
* Installing latest `npm`; if this does not work on your node version, please report a bug!
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm@10.1.0
npm ERR! notsup Not compatible with your version of node/npm: npm@10.1.0
npm ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}
npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v16.20.2"}

npm ERR! A complete log of this run can be found in: /Users/codati/.npm/_logs/2023-09-20T08_29_36_696Z-debug-0.log
* npm upgraded to: v9.6.7

What did you expect to happen?
install npm 9.8.1

Hi,
support for node 16 and lower was dropped with version 10 of npm
npm@10.0.0 { node: '^18.17.0 || >=20.5.0' }
npm@9.8.1 { node: '^14.17.0 || ^16.13.0 || >=18.0.0' }

This is because you’re using an out of date version of nvm. Rerun the nvm install script from the readme, and it should work fine.

i have run
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
but I didn't restart my terminal after that it works now thank you

authors: codati ljharb


text:
Capacitor: sync requires to install the latest version of @capacitor/cli globally

Describe the bug
Running npx nx sync ... will prompt the user to install the latest version of @capacitor/cli globally.
> nx run APPNAME:sync:android

Need to install the following packages:
  @capacitor/cli@4.7.1
Ok to proceed? (y)

To Reproduce
Make a demo project, add @capacitor/cli, @nxext/capacitor and try to run an nx sync... command.
This is how the relevant part of project.json looks like:
    "sync": {
      "executor": "@nxext/capacitor:cap",
      "options": {
        "cmd": "sync"
      },
      "configurations": {
        "ios": {
          "cmd": "sync ios"
        },
        "android": {
          "cmd": "sync android"
        }
      }
    },

Expected behavior
I expected that the @capacitor/cli that is added to the project would be used.
This is important because the latest version of @capacitor/cli has a bug and we would not like to use that version during build.
Additional context
Installing a particular version of @capacitor/cli globally before running sync does not work. The sync command still wants to install the latest @capacitor/cli globally.

Where is the dependency on capacitor/cli even specified?

I think this is related to #915 and the dep was defined in #817

authors: eggbeard mezoistvan

repo: nxext/nx-extensions


text:
Duplicate modulepreload links in head.

Some modulepreload link's are added twice (notice vendor in the case below) in specific manifest cases. My guess it's because of the 3 input scripts, with each slightly different imports in the js itself.
Output in html (domain redacted)
<script type="module" src="/dist/assets/main.168516cf.js" crossorigin></script>
<link href="/dist/assets/Layout.5daf469e.js" rel="modulepreload" crossorigin>
<link href="/dist/assets/vendor.01ab196e.js" rel="modulepreload" crossorigin>
<link href="/dist/assets/vendor.01ab196e.js" rel="modulepreload" crossorigin>
<link href="/dist/assets/main.575548a8.css" rel="stylesheet" media="print" onload="this.media='all'">

Used manifest.json
{
  "src/js/main.js": {
    "file": "assets/main.168516cf.js",
    "src": "src/js/main.js",
    "isEntry": true,
    "imports": [
      "_Layout.5daf469e.js",
      "_vendor.01ab196e.js"
    ],
    "css": [
      "assets/main.575548a8.css"
    ],
    "assets": [
      "assets/Font-Regular.746d0c22.woff2",
      "assets/Font-Regular.1f967c79.woff",
      "assets/Font-Bold.6c627e8a.woff2",
      "assets/Font-Bold.5d3d5626.woff",
      "assets/gradient-category-cta.0cafa9fc.png",
      "assets/footer-bg.b5cbcf69.svg",
      "assets/gradient-bg-mob.7b9a948d.jpg",
      "assets/gradient-bg.d3559d31.jpg",
      "assets/home-footer-bg.3a09858a.png"
    ]
  },
  "src/js/footer.js": {
    "file": "assets/footer.1b22b364.js",
    "src": "src/js/footer.js",
    "isEntry": true,
    "css": [
      "assets/footer.f52685bf.css"
    ],
    "assets": [
      "assets/Font-Regular.746d0c22.woff2",
      "assets/Font-Regular.1f967c79.woff",
      "assets/Font-Bold.6c627e8a.woff2",
      "assets/Font-Bold.5d3d5626.woff"
    ]
  },
  "src/js/menu.js": {
    "file": "assets/menu.02571f38.js",
    "src": "src/js/menu.js",
    "isEntry": true,
    "imports": [
      "_Layout.5daf469e.js",
      "_vendor.01ab196e.js"
    ],
    "css": [
      "assets/menu.b2391e91.css"
    ],
    "assets": [
      "assets/Font-Regular.746d0c22.woff2",
      "assets/Font-Regular.1f967c79.woff",
      "assets/Font-Bold.6c627e8a.woff2",
      "assets/Font-Bold.5d3d5626.woff"
    ]
  },
  "_vendor.01ab196e.js": {
    "file": "assets/vendor.01ab196e.js"
  },
  "_Layout.5daf469e.js": {
    "file": "assets/Layout.5daf469e.js",
    "imports": [
      "_vendor.01ab196e.js"
    ]
  }
}

Versions

Plugin version: 1.0.16
Craft version: Craft Pro 3.7.16

@khalwat, you're right, everything works fine despite the duplicates.


text:
Warning about using debounce together with onSet

Someone (like me) could decide that debounce could be applied here.

I was so stupid


text:
Add Rust 1.75

Require some changes to maek clippy happy.

Closing in favor of https://github.com/o1-labs/proof-systems/pull/1945


text:
LESQ-880: Lesson Listing page slide decks

Description
Music year: 1964

Removes hardcoded false value and returns bool depending on if copyright content is available or not

Issue(s)
Fixes #LESQ-880
How to test

Go to https://deploy-preview-2534--oak-web-application.netlify.thenational.academy
Click on MFL languages which containt copyright
You should see shouldn't display slide deck as available
All other lessons should be un affected

Screenshots
How it used to look (delete if n/a):

How it should now look:

Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

:tada: This PR is included in version 1.473.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: k-huggs oak-machine-user

repo: oaknational/Oak-Web-Application


text:
fix: error colour precedence in message wrapper

Description
Type 'user' was overriding background colour of the chat message box for generic and moderation  error messages on reload of the page.

Change order of classes so errorType has precedence.

Issue(s) - AI-527
https://www.notion.so/oaknationalacademy/Sensitive-warnings-lose-colour-d1b3361edcf7478ea3b04f7be844a7ce
How to test

Go to https://oak-ai-lesson-assistant-p6i18zgf9.vercel-preview.thenational.academy
Create a lesson with sensitive content, refresh the page, sensitive content box remains mint green colour

Checklist

[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Does this PR update a package with a breaking change

Is this your first PR on the repo? If so, welcome! -

Thanks!

I noticed that MessageWrapperProps has type: "user" | "editing" | "warning" | "moderation" | "aila";. Should the type be moderation rather than user?

The type for messages with the changing colour are user with  errorType moderation

 type: "user" | "editing" | "warning" | "moderation" | "aila";
  errorType: "generic" | "moderation" | null;
Should they be coming through as type = moderation ?

:tada: This PR is included in version 1.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: oaknational/oak-ai-lesson-assistant


text:
New reporting

This is WIP PR for introducing new reporting models and report command.
Comments are highly appreciated.

Can one of the admins verify this patch?

Just FYI those doc strings you are specifying in the Report model aren't correctly placed. Docstrings are supposed to follow after the item they are referring to.
Example:
class Foobar(object):
    attribute = fields.Something()
    """ Docstring follows here """

Your documentation is the other way around, it is before the statement that introduces it.

@vinzenz @pirat89 @shaded-enmity anything else we are missing for this first round? If not let's do the final testing. With this PR in, testing the repository PR will be much easier...

@vinzenz all your comments should be hopefully addressed. @bocekm @jmikovic could you please test it? I just did and seems to be working fine. Let me know you need any details.

can we set ID for leapp report to last run, leapp list-runs show only last one anyways

@jmikovic ahh yep, changing the command from opt to arg broke this. @vinzenz is it currently possible to provide nargs='?' to the parser?

@jmikovic @vinzenz @shaded-enmity
Anyway I guess optional ID with last run as default can wait till other iteration. I will get rid of the defaulting as id has to provided anyway.
Apart from that I also moved "list-runs" command to upgrade init as it fits better there , me thinks.

@Rezney Well no it's not possible, but then again, if you want it optional, then don't make it a positional  argument but an option that allows you to specify an ID, otherwise it will be last.

Let's wait with the merge until we have python babel pkg in PES data.

@vinzenz are your requested changes still up-to-date?

As discussed with @Rezney, the blocking rq-changes from @vinzenz has been kept to ensure we will merge it after we the related PR in leapp-repository will be prepared for merge as well. That's it, so removing the request and going to merge that.

authors: Rezney centos-ci jmikovic pirat89 vinzenz

repo: oamg/leapp


text:
Reserved words

How I'm supposed to set from parameter in instrument.candles()? It's a reserved word in Python

You'll notice that "from" and "to" in the rest spec are "fromTime" and "toTime" in the python library:
https://github.com/oanda/v20-python/blob/master/src/v20/instrument.py#L200

authors: alekna dmpettyp


text:
[GLUTEN-2891][VL]fix: Add support to scan Delta Lake tables

What changes were proposed in this pull request?
Adds support to Delta Lake table
(Fixes: #2891)
How was this patch tested?
Manual test

Thanks for the fix, have you try this patch in your test? Velox does not support Delta format as I know, does Delta file can be read as a normal parquet file?

IMO, this is not enough. If enable column mapping, it will return NULL rows. And in Deletion Vector case, there will be some redundant rows.

@YannByron in that case would we need to re-implement Delta features in Velox?
I was expecting Velox to help with Native Scan and some other operators and that Delta would work on top of it applying filters for DV, or changing the column name to scan before sending to Velox. It seems it is not the case.

@felipepessoto
Sorry for the late reply. I saw you have commented in https://github.com/oap-project/gluten/pull/2902. Let's discuss there.

authors: YannByron Yohahaha felipepessoto

repo: oap-project/gluten


text:
Compilation failure if GCC version < 6.1 (C++ 11 Support)

These type traits are only available since C++14:
In file included from /mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:26:0,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:36:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/type_traits.h:45:27: error: expected type-specifier
 using enable_if_boolean = std::enable_if_t<is_boolean_type<T>::value>;
                           ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/type_traits.h:48:26: error: expected type-specifier
 using enable_if_number = std::enable_if_t<is_number_like_type<T>::value>;
                          ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/type_traits.h:58:31: error: expected type-specifier
 using enable_if_string_like = std::enable_if_t<is_string_like_type<T>::value>;
                               ^
In file included from /mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/unsafe_array.h:28:0,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:27,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:36:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/third_party/row_wise_memory/unsafe_row.h:88:37: error: ‘enable_if_t’ in namespace ‘std’ does not name a type
 template <typename T, typename std::enable_if_t<is_number_alike<T>::value>* = nullptr>
                                     ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/third_party/row_wise_memory/unsafe_row.h:88:48: error: expected ‘>’ before ‘<’ token
 template <typename T, typename std::enable_if_t<is_number_alike<T>::value>* = nullptr>
                                                ^
In file included from /mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:27:0,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:36:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/unsafe_array.h:46:34: error: ‘enable_if_number’ was not declared in this scope
 class TypedUnsafeArray<DataType, enable_if_number<DataType>> : public UnsafeArray {
                                  ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/unsafe_array.h:46:34: note: suggested alternative:
In file included from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/arrow/array.h:32:0,
                 from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/gandiva/arrow.h:23,
                 from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/gandiva/expression.h:22,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/code_generator_factory.h:19,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:35:
/mnt/DP_disk1/code/arrow/cpp/build/bundle/include/arrow/type_traits.h:415:66: note:   ‘arrow::enable_if_number’
 using enable_if_number = enable_if_t<is_number_type<T>::value, R>;
                                                                  ^
In file included from /mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:27:0,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:36:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/unsafe_array.h:46:51: error: template argument 2 is invalid
 class TypedUnsafeArray<DataType, enable_if_number<DataType>> : public UnsafeArray {
                                                   ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/unsafe_array.h:46:59: error: expected unqualified-id before ‘>’ token
 class TypedUnsafeArray<DataType, enable_if_number<DataType>> : public UnsafeArray {
                                                           ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/unsafe_array.h:76:34: error: ‘enable_if_string_like’ was not declared in this scope
 class TypedUnsafeArray<DataType, enable_if_string_like<DataType>> : public UnsafeArray {
                                  ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/unsafe_array.h:76:34: note: suggested alternative:
In file included from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/arrow/array.h:32:0,
                 from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/gandiva/arrow.h:23,
                 from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/gandiva/expression.h:22,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/code_generator_factory.h:19,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:35:
/mnt/DP_disk1/code/arrow/cpp/build/bundle/include/arrow/type_traits.h:478:76: note:   ‘arrow::enable_if_string_like’
 using enable_if_string_like = enable_if_t<is_string_like_type<T>::value, R>;
                                                                            ^
In file included from /mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:27:0,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:36:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/unsafe_array.h:76:56: error: template argument 2 is invalid
 class TypedUnsafeArray<DataType, enable_if_string_like<DataType>> : public UnsafeArray {
                                                        ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/precompile/unsafe_array.h:76:64: error: expected unqualified-id before ‘>’ token
 class TypedUnsafeArray<DataType, enable_if_string_like<DataType>> : public UnsafeArray {
                                                                ^
In file included from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:36:0:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:32:40: error: ‘sparkcolumnarplugin::precompile::enable_if_number’ has not been declared
 using sparkcolumnarplugin::precompile::enable_if_number;
                                        ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:33:40: error: ‘sparkcolumnarplugin::precompile::enable_if_string_like’ has not been declared
 using sparkcolumnarplugin::precompile::enable_if_string_like;
                                        ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:56:41: error: ‘enable_if_number’ was not declared in this scope
 class TypedHashRelationColumn<DataType, enable_if_number<DataType>>
                                         ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:56:41: note: suggested alternative:
In file included from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/arrow/array.h:32:0,
                 from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/gandiva/arrow.h:23,
                 from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/gandiva/expression.h:22,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/code_generator_factory.h:19,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:35:
/mnt/DP_disk1/code/arrow/cpp/build/bundle/include/arrow/type_traits.h:415:66: note:   ‘arrow::enable_if_number’
 using enable_if_number = enable_if_t<is_number_type<T>::value, R>;
                                                                  ^
In file included from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:36:0:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:56:58: error: template argument 2 is invalid
 class TypedHashRelationColumn<DataType, enable_if_number<DataType>>
                                                          ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:56:66: error: expected unqualified-id before ‘>’ token
 class TypedHashRelationColumn<DataType, enable_if_number<DataType>>
                                                                  ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:86:41: error: ‘enable_if_string_like’ was not declared in this scope
 class TypedHashRelationColumn<DataType, enable_if_string_like<DataType>>
                                         ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:86:41: note: suggested alternative:
In file included from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/arrow/array.h:32:0,
                 from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/gandiva/arrow.h:23,
                 from /mnt/DP_disk1/code/arrow/cpp/build/bundle/include/gandiva/expression.h:22,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/code_generator_factory.h:19,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:35:
/mnt/DP_disk1/code/arrow/cpp/build/bundle/include/arrow/type_traits.h:478:76: note:   ‘arrow::enable_if_string_like’
 using enable_if_string_like = enable_if_t<is_string_like_type<T>::value, R>;
                                                                            ^
In file included from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:36:0:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:86:63: error: template argument 2 is invalid
 class TypedHashRelationColumn<DataType, enable_if_string_like<DataType>>
                                                               ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:86:71: error: expected unqualified-id before ‘>’ token
 class TypedHashRelationColumn<DataType, enable_if_string_like<DataType>>
                                                                       ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:193:27: error: ‘enable_if_t’ in namespace ‘std’ does not name a type
             typename std::enable_if_t<!std::is_same<KeyArrayType, StringArray>::value>* =
                           ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:193:38: error: expected ‘>’ before ‘<’ token
             typename std::enable_if_t<!std::is_same<KeyArrayType, StringArray>::value>* =
                                      ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:254:27: error: ‘enable_if_t’ in namespace ‘std’ does not name a type
             typename std::enable_if_t<is_number_alike<CType>::value>* = nullptr>
                           ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:254:38: error: expected ‘>’ before ‘<’ token
             typename std::enable_if_t<is_number_alike<CType>::value>* = nullptr>
                                      ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:284:27: error: ‘enable_if_t’ in namespace ‘std’ does not name a type
             typename std::enable_if_t<is_number_alike<CType>::value>* = nullptr>
                           ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:284:38: error: expected ‘>’ before ‘<’ token
             typename std::enable_if_t<is_number_alike<CType>::value>* = nullptr>
                                      ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:307:27: error: ‘enable_if_t’ in namespace ‘std’ does not name a type
             typename std::enable_if_t<is_number_alike<CType>::value>* = nullptr>
                           ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:307:38: error: expected ‘>’ before ‘<’ token
             typename std::enable_if_t<is_number_alike<CType>::value>* = nullptr>
                                      ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:335:27: error: ‘enable_if_t’ in namespace ‘std’ does not name a type
             typename std::enable_if_t<is_number_alike<CType>::value>* = nullptr>
                           ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/codegen/common/hash_relation.h:335:38: error: expected ‘>’ before ‘<’ token
             typename std::enable_if_t<is_number_alike<CType>::value>* = nullptr>
                                      ^
In file included from /mnt/DP_disk1/code/native-sql-engine/cpp/src/shuffle/splitter.h:32:0,
                 from /mnt/DP_disk1/code/native-sql-engine/cpp/src/jni/jni_wrapper.cc:42:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/shuffle/utils.h: In function ‘arrow::Result<std::vector<sparkcolumnarplugin::shuffle::Type::typeId> > sparkcolumnarplugin::shuffle::ToSplitterTypeId(const std::vector<std::shared_ptr<arrow::Field> >&)’:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/shuffle/utils.h:122:18: error: ‘cbegin’ is not a member of ‘std’
   std::transform(std::cbegin(fields), std::cend(fields),
                  ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/shuffle/utils.h:122:39: error: ‘cend’ is not a member of ‘std’
   std::transform(std::cbegin(fields), std::cend(fields),
                                       ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/shuffle/utils.h: In function ‘int64_t sparkcolumnarplugin::shuffle::GetBufferSizes(const std::shared_ptr<arrow::Array>&)’:
/mnt/DP_disk1/code/native-sql-engine/cpp/src/shuffle/utils.h:179:26: error: ‘cbegin’ is not a member of ‘std’
   return std::accumulate(std::cbegin(buffers), std::cend(buffers), 0LL,
                          ^
/mnt/DP_disk1/code/native-sql-engine/cpp/src/shuffle/utils.h:179:48: error: ‘cend’ is not a member of ‘std’
   return std::accumulate(std::cbegin(buffers), std::cend(buffers), 0LL,

ska_sort requires for C++14 so it's not possible to get back to 11. Closing.

repo: oap-project/native-sql-engine


text:
Add or modify option to allow providing a single schema instead of directory

suggested by @rpiazza

actually, this isn't exactly what I was suggesting.  You might have a lot of extensions - so it would look like this:
stix2_validator --additional-schema-dir /path/to/my/extension-schemas <stix_file.json>

authors: clenk rpiazza

repo: oasis-open/cti-stix-validator


text:
Helpers for compile-time runtime ID embedding

Runtime identifiers should be part of the compiled binary. We should add helpers to enable build scripts to easily embed these into runtimes.

This should likely be done at runtime, closing this in favor of #2519.

authors: Yawning kostko

repo: oasislabs/oasis-core


text:
unmnemonic: Add support for bitpie flavored derivation.

Forgot about this.  It is a continuation of https://github.com/oasisprotocol/tools/tree/unmnemonic/bitpie that works as far as I can tell.
Fixes #10

And yes, this unfortunately requires a secp256k1 BIP-0032 implementation as a dependency because the bitpie variant is interesting.

repo: oasisprotocol/tools


text:
More events

Add more autocmd entries.

What a useful event, thank you!

authors: obcat thinca

repo: obcat/vim-hitspop


text:
Generate definitions for instances with duplicate (or missing) definitions

Many instances of organization (such as eBioscience) share the definition:

A supplier of flow cytometry analyzers

We can auto-generate a definition based on the label of the instance and its asserted type, e.g.:

A particular organization that is named eBioscience.

Based on the fact that eBioscience has the two type axioms:

organization
'has role' some 'manufacturer role'

We could potentially include the anonymous type axiom, as well:

A particular organization named eBioscience that has role manufacturer role.

... or something along those lines. The implementation would be a SPARQL query, which is pretty straightforward. I would appreciate feedback on which version of the definition would be better.

I would only use the asserted parent class.

repo: obi-ontology/obi


text:
info

Hello
synchronized lyrics are only done manually?
Thank You

For now, yes. But I have plans of some kinds of lyric search in my backlog, expect this feature in the future

authors: AinzOoalGown-fun obillekyle