fedora-docs-l10n/packaging-guidelines/master/pages/Node.js

Zen

Translation

English type: Title ==

French

Needs editing

Skip

	English	French	Actions
	Node.js Packaging Guidelines
	The upstream Node.js stance on https://nodejs.org/en/blog/npm/npm-1-0-global-vs-local-installation/[global library packages] is that they are ".. best avoided if not needed." In Fedora, we take the same stance with our nodejs packages. You can provide a package that uses nodejs, but you should bundle all the nodejs libraries that are needed.
	What to Package
	The interpreter, development headers/libraries, and the assorted tools to manage project-level installations.
	Examples: nodejs, npm, yarn
	Packages that provide applications that users would want to use in their shell.
	Examples: uglify
	Naming Guidelines	Directives de nommage
	Application packages that mainly provide tools (as opposed to libraries) that happen to be written for Node.js must follow the general xref:Naming.adoc[Naming Guidelines] instead.
	The name of a Node.js extension/library package must start with _nodejs-_ then the upstream name or name used in the npm registry. For example: _nodejs-foomodule_. While it is uncommon for a package's name to contain _node_, if it does, you should still add the nodejs prefix. For instance, the npm registry contains a _uuid_ and a _node-uuid_ module, which would need to be named _nodejs-uuid_ and _nodejs-node-uuid_, repsectively.
	BuildRequires
	To build a package that is a nodejs module, bundles or uses nodejs modules, or needs nodejs for building or testing, you need to have:
	BuildRequires: nodejs-devel
	Macros	Macros
	The following macros are defined for you:
	\|Macro \|Normal Definition \|Notes \|__nodejs \|%\{_bindir}/node \|The Node.js interpreter \|nodejs_version \|e.g. 0.9.5 \|The currently installed version of Node.js. \|nodejs_sitelib \|%\{_prefix}/lib/node_modules \|Where Node.js modules written purely in JavaScript are installed \|nodejs_sitearch \|%\{_prefix}/lib/node_modules \|Where native C++ Node.js modules are installed \|nodejs_symlink_deps \|%\{_prefix}/lib/rpm/nodejs-symlink-deps \|See <<Symlinking Dependencies>> below. \|nodejs_fixdep \|%\{_prefix}/lib/rpm/nodejs-fixdep \|See <<Correcting Dependencies>> below. \|nodejs_arches \|%\{ix86} x86_64 %\{arm} \|See #ExclusiveArch. This macro is provided by `+redhat-rpm-config+` in F19+ so it works with Koji properly. \|nodejs_default_filter \|%global __provides_exclude_from ^%\{nodejs_sitearch}/.*\\.node$ \|Filters unwanted provides from native modules. See <<Filtering Unwanted Provides>> below.
	These macros are provided by the _nodejs-packaging_ package.
	During `+%install+` or when listing `+%files+` you can use the `+%nodejs_sitelib+` or `+%nodejs_sitearch+` macro to specify where the installed modules are to be found. For instance:
	%files # A pure JavaScript node module %{nodejs_sitelib}/foomodule/ # A native node module %{nodejs_sitearch}/barmodule/
	Using this macro instead of hardcoding the directory in the specfile ensures your spec remains compatible with the installed Node.js version even if the directory structure changes radically (for instance, if `+%nodejs_sitelib+` moves into `+%{_datadir}+`).
	ExclusiveArch
	The V8 JavaScript runtime used by Node.js uses a Just-in-Time (JIT) compiler that is specially tuned to individual architectures, and must be manually ported to any new architectures that wish to support it. Node.js packages must include an ExclusiveArch line that restricts them to only these architectures.
	The `+%{nodejs_arches}+` macro is provided to make this easy, so pure JavaScript packages must use:
	ExclusiveArch: %{nodejs_arches} noarch
	Native (binary) packages must omit `+noarch+` and list only `+%{nodejs_arches}+` or the list of architectures as appropriate.
	Bundled Licenses
	The licenses of the bundled Node.js modules need to be in the spec file. If you are using our bundling script, they will be listed in `+<package>-<version>-bundled-licenses.txt+`. It is recommended that you include `+<package>-<version>-bundled-licenses.txt+` in the rpm.
	Each time you update your package, you need to verify the bundled licenses against https://docs.fedoraproject.org/en-US/legal/allowed-licenses/[Fedoras Software License List]. Note that precompiled/minimized JavaScript may be packaged, but the requirement to verify the licenses also applies to it, see the :xref:JavaScript.adoc[JavaScript guidelines].
	List all unique licenses on the License: line of your spec file. https://docs.fedoraproject.org/en-US/legal/license-field/#_basic_rule[Separate each license with the word "and"].

Loading…

harmful-breeze

Translation changed

English

French 2 characters edited Current translation Translated

9 days ago

harmful-breeze

Suggestion accepted

English

French 8 characters edited Translated

9 days ago

mt:weblate-translation-memory

Suggestion added

English

French 8 characters edited

13 days ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Unchanged translation

Source and translation are identical

Reset

Glossary

English	French
No related strings found in the glossary.

997773 String information

Source string description

type: Title ==

Flags

no-wrap

Source string location

pages/Node.js.adoc:26

String age

4 years ago

Last updated

9 days ago

Source string age

4 years ago

Translation file

po/fr/master/pages/Node.js.po, string 14

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.