Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address frontend deprecation warnings #87

Open
chadwcarlson opened this issue Nov 7, 2023 · 1 comment
Open

Address frontend deprecation warnings #87

chadwcarlson opened this issue Nov 7, 2023 · 1 comment

Comments

@chadwcarlson
Copy link
Contributor

chadwcarlson commented Nov 7, 2023

Currently the frontend build includes npm WARN deprecated. Address this:

Processing activity: Chad Carlson pushed to Default-v2
    Found 233 commits

    Building application 'frontend' (runtime type: nodejs:18, tree: 8758b3d)
      Generating runtime configuration.
      
      Executing build hook...
        W: npm WARN deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.
        W: npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
        W: npm WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
        W: npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
        W: npm WARN deprecated [email protected]: [email protected]
        W: npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.
        W: npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
        W: npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.
        W: npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.
        W: npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
        W: npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
        W: npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
        
        added 1613 packages, and audited 1614 packages in 31s
        
        286 packages are looking for funding
          run `npm fund` for details
        
        3 moderate severity vulnerabilities
        
        To address all issues (including breaking changes), run:
          npm audit fix --force
        
        Run `npm audit` for details.
        W: npm notice 
        W: npm notice New major version of npm available! 9.6.7 -> 10.2.3
        W: npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.2.3
        W: npm notice Run npm install -g [email protected] to update!
        W: npm notice 
        
        > [email protected] build
        > react-scripts build
        
        Creating an optimized production build...
        Compiled with warnings.
        
        [eslint] 
        src/utility/api.ts
          Line 30:17:  Expected '===' and instead saw '=='  eqeqeq
          Line 32:24:  Expected '===' and instead saw '=='  eqeqeq
          Line 34:31:  Expected '===' and instead saw '=='  eqeqeq
          Line 39:31:  Expected '===' and instead saw '=='  eqeqeq
          Line 44:31:  Expected '===' and instead saw '=='  eqeqeq
          Line 49:31:  Expected '===' and instead saw '=='  eqeqeq
        
        Search for the keywords to learn more about each warning.
        To ignore, add // eslint-disable-next-line to the line before.
@tylers-username
Copy link
Collaborator

The eslint issue is resolved over here: #84

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

No branches or pull requests

2 participants